Btrfs: don't allocate a seperate csums array for direct reads

Browse source

We've been allocating a big array for csums instead of storing them in the
io_tree like we do for buffered reads because previously we were locking the
entire range, so we didn't have an extent state for each sector of the
range.  But now that we do the range locking as we map the buffers we can
limit the mapping lenght to sectorsize and use the private part of the
io_tree for our csums.  This allows us to avoid an extra memory allocation
for direct reads which could incur latency.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>

...

This commit is contained in:

Josef Bacik 2012-08-03 16:49:19 -04:00 • committed by Chris Mason

parent 99f5944b84

commit c329861da4

3 changed files with 19 additions and 32 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

2

fs/btrfs/ctree.h

View file

4

fs/btrfs/file-item.c

View file

45

fs/btrfs/inode.c

View file