summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2022-03-15 18:22:37 +0300
committerDavid Sterba <dsterba@suse.com>2022-05-16 18:03:09 +0300
commit1c6cbbbeeeca5702c115f4547fd0f75a7fc0f911 (patch)
treef717e889bf08c1ff933452c331fcd039d9b9bf8e /tools/perf/scripts/python/exported-sql-viewer.py
parent831e1ee60216534c54f2e240f9586d6cfe29b1c2 (diff)
downloadlinux-1c6cbbbeeeca5702c115f4547fd0f75a7fc0f911.tar.xz
btrfs: remove inode_dio_wait() calls when starting reflink operations
When starting a reflink operation we have these calls to inode_dio_wait() which used to be needed because direct IO writes that don't cross the i_size boundary did not take the inode's VFS lock, so we could race with them and end up with ordered extents in target range after calling btrfs_wait_ordered_range(). However that is not the case anymore, because the inode's VFS lock was changed from a mutex to a rw semaphore, by commit 9902af79c01a8e ("parallel lookups: actual switch to rwsem"), and several years later we started to lock the inode's VFS lock in shared mode for direct IO writes that don't cross the i_size boundary (commit e9adabb9712ef9 ("btrfs: use shared lock for direct writes within EOF")). So remove those inode_dio_wait() calls. Signed-off-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions