Qu Wenruo 43eb5f2975 btrfs: Introduce extent_io_tree::owner to distinguish different io_trees ... Btrfs has the following different extent_io_trees used: - fs_info::free_extents[2] - btrfs_inode::io_tree - for both normal inodes and the btree inode - btrfs_inode::io_failure_tree - btrfs_transaction::dirty_pages - btrfs_root::dirty_log_pages If we want to trace changes in those trees, it will be pretty hard to distinguish them. Instead of using hard-to-read pointer address, this patch will introduce a new member extent_io_tree::owner to track the owner. This modification needs all the callers of extent_io_tree_init() to accept a new parameter @owner. This patch provides the basis for later trace events. Signed-off-by: Qu Wenruo <wqu@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>		2019-04-29 19:02:18 +02:00
..
btrfs-tests.c	btrfs: Introduce extent_io_tree::owner to distinguish different io_trees	2019-04-29 19:02:18 +02:00
btrfs-tests.h
extent-buffer-tests.c
extent-io-tests.c	btrfs: Introduce extent_io_tree::owner to distinguish different io_trees	2019-04-29 19:02:18 +02:00
extent-map-tests.c
free-space-tests.c
free-space-tree-tests.c
inode-tests.c
qgroup-tests.c