btrfs: use a separate end_io handler for read_extent_buffer

Browse source

Now that we always use a single bio to read an extent_buffer, the buffer
can be passed to the end_io handler as private data.  This allows
implementing a much simplified dedicated end I/O handler for metadata
reads.

Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: David Sterba <dsterba@suse.com>

...

This commit is contained in:

Christoph Hellwig 2023-05-03 17:24:28 +02:00 • committed by David Sterba

parent e194931076

commit 046b562b20

3 changed files with 41 additions and 149 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

105

fs/btrfs/disk-io.c

View file

5

fs/btrfs/disk-io.h

View file

80

fs/btrfs/extent_io.c

View file