Commit ce195332 authored Sep 25, 2012 by Josef Bacik Committed by Chris Mason Oct 09, 2012

Btrfs: do not hold the file extent leaf locked when adding extent item

For some reason we unlock everything except the leaf we are on, set the path
blocking and then add the extent item for the extent we just finished
writing. I can't for the life of me figure out why we would want to do
this, and the history doesn't really indicate that there was a real reason
for it, so just remove it. This will reduce our tree lock contention on
heavy writes. Thanks,

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

parent de0022b9

fs/btrfs/inode.c

+1 −3

Original line number	Diff line number	Diff line
		@@ -1822,10 +1822,8 @@ static int insert_reserved_file_extent(struct btrfs_trans_handle *trans,
		btrfs_set_file_extent_encryption(leaf, fi, encryption);
		btrfs_set_file_extent_other_encoding(leaf, fi, other_encoding);

		btrfs_unlock_up_safe(path, 1);
		btrfs_set_lock_blocking(leaf);

		btrfs_mark_buffer_dirty(leaf);
		btrfs_release_path(path);

		inode_add_bytes(inode, num_bytes);

Admin message