btrfs: only reserve metadata_size for inodes
Historically we reserved worst case for every btree operation, and generally speaking we want to do that in cases where it could be the worst case. However for updating inodes we know the inode items are already in the tree, so it will only be an update operation and never an insert operation. This allows us to always reserve only the metadata_size amount for inode updates rather than the insert_metadata_size amount. Reviewed-by: Nikolay Borisov <nborisov@suse.com> Signed-off-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
committed by
David Sterba
parent
2bd36e7b4f
commit
bcacf5f3f9
@ -612,7 +612,7 @@ static int btrfs_delayed_inode_reserve_metadata(
|
||||
src_rsv = trans->block_rsv;
|
||||
dst_rsv = &fs_info->delayed_block_rsv;
|
||||
|
||||
num_bytes = btrfs_calc_insert_metadata_size(fs_info, 1);
|
||||
num_bytes = btrfs_calc_metadata_size(fs_info, 1);
|
||||
|
||||
/*
|
||||
* btrfs_dirty_inode will update the inode under btrfs_join_transaction
|
||||
|
Reference in New Issue
Block a user