btrfs: trace: Add trace events for extent_io_tree
Subsystems (2)
v2 cover btrfs: trace: Add trace events for extent_io_tree
This patchset can be fetched from github:
https://github.com/adam900710/linux/tree/ftrace_extent_io_tree
Which is based on v5.0-rc7 tag.
Btrfs uses (almost abuse) extent_io_tree for a lot of operations, e.g:
- Tree block locking
BTRFS_I(btree_inode)->io_tree
- Page status tracing
BTRFS_I(file_inode)->io_tree and BTRFS_I(file_inode)->io_failure_tree transaction->dirty_pages
- Pinned down extents tracing
fs_info->freed_extents[2]
...
However we don't have any trace events for us to understand how btrfs works.
This patchset will introduce trace events for
set/clear/convert_extent_bit().
Despite that, there are some other small modifications required:
- Introduce extent_io_tree::fs_info
For trace events to output fsid to distinguish different fs. This increase the size of extent_io_tree by 8 bytes.
- Allow NULL fs_info for TP_fast_assign_fsid()
There is extent bits operation in selftest which is too deep to pass fs_info. And since it's in selftest, it shouldn't trigger trace events.
But to be safe, we still need to check fs_indo in TP_fast_assign_fsid(), for NULL fs_info, just keep fsid filled with zero.
- New extent_io_tree::owner
To distinguish different extent io trees. It uses the unpopulated bits of original trace_uptodate, so it doesn't increase the size of extent_io_tree.
The output examples and extra notes are: (copied from the 3rd patch)
btrfs_set_extent_bit: <FDID>: io_tree=IO_TREE ino=1 root=1 start=22036480 len=4096 set_bits=LOCKED
btrfs_set_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22040576 len=4096 set_bits=LOCKED
btrfs_set_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22044672 len=4096 set_bits=LOCKED
btrfs_set_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22048768 len=4096 set_bits=LOCKED
btrfs_clear_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22036480 len=16384 clear_bits=LOCKED ^^^ Extent buffer 22036480 read from disc, the locking progress
btrfs_set_extent_bit: <FSID>: io_tree=TRANS_DIRTY_PAGES ino=1 root=1 start=30425088 len=16384 set_bits=DIRTY
btrfs_set_extent_bit: <FSID>: io_tree=TRANS_DIRTY_PAGES ino=1 root=1 start=30441472 len=16384 set_bits=DIRTY ^^^ 2 new tree blocks allocated in one transaction
btrfs_set_extent_bit: <FSID>: io_tree=FREED_EXTENTS0 ino=0 root=0 start=30523392 len=16384 set_bits=DIRTY
btrfs_set_extent_bit: <FSID>: io_tree=FREED_EXTENTS0 ino=0 root=0 start=30556160 len=16384 set_bits=DIRTY ^^^ 2 old tree blocks get pinned down
There is one point which need extra attention:
1) Those trace events are pretty heavy
The following workload would generate over 400 trace events.
mkfs.btrfs -f $dev
start_trace
mount $dev $mnt -o enospc_debug
sync
touch $mnt/file1
touch $mnt/file2
touch $mnt/file3
xfs_io -f -c "pwrite 0 16k" $mnt/file4
umount $mnt
end_trace
It's not recommended to use them in real world environment.
Changelog:
v2:
- Introduce fs_info to distinguish different btrfs filesystems
- Code style change to make trace code more elegant
- Minor IO_TREE_* naming change.
- Use btrfs_ino() to replace raw inode number.
- Change extent_io_tree::owner declaration to avoid affecting spinlock.
Qu Wenruo (3):
btrfs: Introduce fs_info for extent_io_tree
btrfs: Introduce extent_io_tree::owner to distinguish different
io_trees
btrfs: trace: Add trace events for extent_io_tree
fs/btrfs/disk-io.c | 12 ++- fs/btrfs/extent_io.c | 9 +- fs/btrfs/extent_io.h | 22 ++++- fs/btrfs/inode.c | 6 +- fs/btrfs/relocation.c | 9 +- fs/btrfs/tests/btrfs-tests.c | 6 +- fs/btrfs/tests/extent-io-tests.c | 2 +- fs/btrfs/transaction.c | 4 +- include/trace/events/btrfs.h | 159 ++++++++++++++++++++++++++++++- 9 files changed, 210 insertions(+), 19 deletions(-)
Signature · 1 line
2.21.0
PATCH v2 1/3 btrfs: Introduce fs_info for extent_io_tree
This patch will introduce a new member, fs_info for extent_io_tree.
This provides the basis for later ftrace events to distinguish the output between different btrfs filesystems.
--- fs/btrfs/disk-io.c | 8 ++++---- fs/btrfs/extent_io.c | 5 +++-- fs/btrfs/extent_io.h | 4 +++- fs/btrfs/inode.c | 4 ++-- fs/btrfs/relocation.c | 8 ++++---- fs/btrfs/tests/btrfs-tests.c | 4 ++-- fs/btrfs/tests/extent-io-tests.c | 2 +- fs/btrfs/transaction.c | 2 +- 8 files changed, 20 insertions(+), 17 deletions(-)
fs/btrfs/disk-io.c +4 -4
@@ -1205,7 +1205,7 @@ static void __setup_root(struct btrfs_root *root, struct btrfs_fs_info *fs_info, root->log_transid_committed =-1 ; root->last_log_commit =0 ;if (!dummy) -extent_io_tree_init (&root->dirty_log_pages,NULL ); +extent_io_tree_init (fs_info, &root->dirty_log_pages,NULL );memset (&root->root_key,0 ,sizeof (root->root_key));memset (&root->root_item,0 ,sizeof (root->root_item));
@@ -2129,7 +2129,7 @@ static void btrfs_init_btree_inode(struct btrfs_fs_info *fs_info) inode->i_mapping->a_ops = &btree_aops;RB_CLEAR_NODE (&BTRFS_I (inode)->rb_node); -extent_io_tree_init (&BTRFS_I (inode)->io_tree, inode); +extent_io_tree_init (fs_info, &BTRFS_I (inode)->io_tree, inode);BTRFS_I (inode)->io_tree.track_uptodate =0 ;extent_map_tree_init (&BTRFS_I (inode)->extent_tree);
@@ -2739,8 +2739,8 @@ int open_ctree(struct super_block *sb, fs_info->block_group_cache_tree =RB_ROOT ; fs_info->first_logical_byte = (u64)-1 ; -extent_io_tree_init (&fs_info->freed_extents[0 ],NULL ); -extent_io_tree_init (&fs_info->freed_extents[1 ],NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[0 ],NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[1 ],NULL ); fs_info->pinned_extents = &fs_info->freed_extents[0 ];set_bit (BTRFS_FS_BARRIER , &fs_info->flags);
fs/btrfs/extent_io.c +3 -2
@@ -200,9 +200,10 @@ void __cold extent_io_exit(void)bioset_exit (&btrfs_bioset); } -void extent_io_tree_init (struct extent_io_tree *tree, -void *private_data) +void extent_io_tree_init (struct btrfs_fs_info *fs_info, +struct extent_io_tree *tree,void *private_data) { + tree->fs_info = fs_info; tree->state =RB_ROOT ; tree->ops =NULL ; tree->dirty_bytes =0 ;
fs/btrfs/extent_io.h +3 -1
@@ -109,6 +109,7 @@ struct extent_io_ops {struct extent_io_tree {struct rb_root state; +struct btrfs_fs_info *fs_info;void *private_data;u64 dirty_bytes;int track_uptodate;
@@ -240,7 +241,8 @@ typedef struct extent_map *(get_extent_t)(struct btrfs_inode *inode, u64 start, u64 len, int create); -void extent_io_tree_init (struct extent_io_tree *tree,void *private_data); +void extent_io_tree_init (struct btrfs_fs_info *fs_info, +struct extent_io_tree *tree,void *private_data);int try_release_extent_mapping (struct page *page,gfp_t mask);int try_release_extent_buffer (struct page *page); int lock_extent_bits(struct extent_io_tree *tree, u64 start, u64 end,
fs/btrfs/inode.c +2 -2
@@ -9128,8 +9128,8 @@ struct inode *btrfs_alloc_inode(struct super_block *sb) inode = &ei->vfs_inode;extent_map_tree_init (&ei->extent_tree); -extent_io_tree_init (&ei->io_tree, inode); -extent_io_tree_init (&ei->io_failure_tree, inode); +extent_io_tree_init (fs_info, &ei->io_tree, inode); +extent_io_tree_init (fs_info, &ei->io_failure_tree, inode); ei->io_tree.track_uptodate =1 ; ei->io_failure_tree.track_uptodate =1 ;atomic_set (&ei->sync_writers,0 );
fs/btrfs/relocation.c +4 -4
@@ -4164,7 +4164,7 @@ struct inode *create_reloc_inode(struct btrfs_fs_info *fs_info,return inode; } -static struct reloc_control *alloc_reloc_control (void ) +static struct reloc_control *alloc_reloc_control (struct btrfs_fs_info *fs_info) {struct reloc_control *rc;
@@ -4175,7 +4175,7 @@ static struct reloc_control *alloc_reloc_control(void)INIT_LIST_HEAD (&rc->reloc_roots);backref_cache_init (&rc->backref_cache);mapping_tree_init (&rc->reloc_root_tree); -extent_io_tree_init (&rc->processed_blocks,NULL ); +extent_io_tree_init (fs_info, &rc->processed_blocks,NULL );return rc; }
@@ -4217,7 +4217,7 @@ int btrfs_relocate_block_group(struct btrfs_fs_info *fs_info, u64 group_start)return -ETXTBSY ; } - rc =alloc_reloc_control (); + rc =alloc_reloc_control (fs_info);if (!rc) {btrfs_put_block_group (bg);return -ENOMEM ;
@@ -4413,7 +4413,7 @@ int btrfs_recover_relocation(struct btrfs_root *root)if (list_empty (&reloc_roots)) goto out; - rc =alloc_reloc_control (); + rc =alloc_reloc_control (fs_info);if (!rc) { err = -ENOMEM ; goto out;
fs/btrfs/tests/btrfs-tests.c +2 -2
@@ -115,8 +115,8 @@ struct btrfs_fs_info *btrfs_alloc_dummy_fs_info(u32 nodesize, u32 sectorsize)INIT_LIST_HEAD (&fs_info->tree_mod_seq_list);INIT_RADIX_TREE (&fs_info->buffer_radix,GFP_ATOMIC );INIT_RADIX_TREE (&fs_info->fs_roots_radix,GFP_ATOMIC ); -extent_io_tree_init (&fs_info->freed_extents[0 ],NULL ); -extent_io_tree_init (&fs_info->freed_extents[1 ],NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[0 ],NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[1 ],NULL ); fs_info->pinned_extents = &fs_info->freed_extents[0 ];set_bit (BTRFS_FS_STATE_DUMMY_FS_INFO , &fs_info->fs_state);
fs/btrfs/tests/extent-io-tests.c +1 -1
@@ -77,7 +77,7 @@ static int test_find_delalloc(u32 sectorsize)return -ENOMEM ; } -extent_io_tree_init (&tmp,NULL ); +extent_io_tree_init (NULL , &tmp,NULL );/* * First go through and create and mark all of our pages dirty, we pin
fs/btrfs/transaction.c +1 -1
@@ -273,7 +273,7 @@ static noinline int join_transaction(struct btrfs_fs_info *fs_info,INIT_LIST_HEAD (&cur_trans->deleted_bgs);spin_lock_init (&cur_trans->dropped_roots_lock);list_add_tail (&cur_trans->list, &fs_info->trans_list); -extent_io_tree_init (&cur_trans->dirty_pages, +extent_io_tree_init (fs_info, &cur_trans->dirty_pages, fs_info->btree_inode); fs_info->generation++; cur_trans->transid = fs_info->generation;
Signature · 1 line
2.21.0
PATCH v2 2/3 btrfs: Introduce extent_io_tree::owner to distinguish different io_trees
In reply to Qu WenruoBtrfs has the following different extent_io_trees used:
- fs_info::free_extents[2]
- btrfs_inode::io_tree
For both normal inodes and btree inode
- btrfs_inode::io_failure_tree
- btrfs_transaction::dirty_pages
- btrfs_root::dirty_log_pages
If we want to trace bits change in those io_trees, it will be pretty hard to distinguish them.
Instead of using hard-to-read pointer address, this patch will introduc a new member extent_io_tree::owner, which uses the unpopulated bits of extent_io_tree::track_uptodate, to track who owns this extent_io_tree.
This modification needs all the callers of extent_io_tree_init() to accept a new parameter @owner.
This patch provides the basis for later ftrace events.
--- fs/btrfs/disk-io.c | 12 ++++++++---- fs/btrfs/extent_io.c | 4 +++- fs/btrfs/extent_io.h | 22 +++++++++++++++++++--- fs/btrfs/inode.c | 6 ++++-- fs/btrfs/relocation.c | 3 ++- fs/btrfs/tests/btrfs-tests.c | 6 ++++-- fs/btrfs/tests/extent-io-tests.c | 2 +- fs/btrfs/transaction.c | 2 +- 8 files changed, 42 insertions(+), 15 deletions(-)
fs/btrfs/disk-io.c +8 -4
@@ -1205,7 +1205,8 @@ static void __setup_root(struct btrfs_root *root, struct btrfs_fs_info *fs_info, root->log_transid_committed =-1 ; root->last_log_commit =0 ;if (!dummy) -extent_io_tree_init (fs_info, &root->dirty_log_pages,NULL ); +extent_io_tree_init (fs_info, &root->dirty_log_pages, +IO_TREE_ROOT_DIRTY_LOG_PAGES ,NULL );memset (&root->root_key,0 ,sizeof (root->root_key));memset (&root->root_item,0 ,sizeof (root->root_item));
@@ -2129,7 +2130,8 @@ static void btrfs_init_btree_inode(struct btrfs_fs_info *fs_info) inode->i_mapping->a_ops = &btree_aops;RB_CLEAR_NODE (&BTRFS_I (inode)->rb_node); -extent_io_tree_init (fs_info, &BTRFS_I (inode)->io_tree, inode); +extent_io_tree_init (fs_info, &BTRFS_I (inode)->io_tree, +IO_TREE_INODE_IO_TREE , inode);BTRFS_I (inode)->io_tree.track_uptodate =0 ;extent_map_tree_init (&BTRFS_I (inode)->extent_tree);
@@ -2739,8 +2741,10 @@ int open_ctree(struct super_block *sb, fs_info->block_group_cache_tree =RB_ROOT ; fs_info->first_logical_byte = (u64)-1 ; -extent_io_tree_init (fs_info, &fs_info->freed_extents[0 ],NULL ); -extent_io_tree_init (fs_info, &fs_info->freed_extents[1 ],NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[0 ], +IO_TREE_FS_INFO_FREED_EXTENTS0 ,NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[1 ], +IO_TREE_FS_INFO_FREED_EXTENTS1 ,NULL ); fs_info->pinned_extents = &fs_info->freed_extents[0 ];set_bit (BTRFS_FS_BARRIER , &fs_info->flags);
fs/btrfs/extent_io.c +3 -1
@@ -201,7 +201,8 @@ void __cold extent_io_exit(void) }void extent_io_tree_init (struct btrfs_fs_info *fs_info, -struct extent_io_tree *tree,void *private_data) +struct extent_io_tree *tree,unsigned int owner, +void *private_data) { tree->fs_info = fs_info; tree->state =RB_ROOT ;
@@ -209,6 +210,7 @@ void extent_io_tree_init(struct btrfs_fs_info *fs_info, tree->dirty_bytes =0 ;spin_lock_init (&tree->lock); tree->private_data = private_data; + tree->owner = owner; }static struct extent_state *alloc_extent_state (gfp_t mask)
fs/btrfs/extent_io.h +19 -3
@@ -107,12 +107,27 @@ struct extent_io_ops { int mirror); }; +enum { +IO_TREE_FS_INFO_FREED_EXTENTS0 , +IO_TREE_FS_INFO_FREED_EXTENTS1 , +IO_TREE_INODE_IO_TREE , +IO_TREE_INODE_IO_FAILURE_TREE , +IO_TREE_RELOC_BLOCKS , +IO_TREE_TRANSACTION_DIRTY_PAGES , +IO_TREE_ROOT_DIRTY_LOG_PAGES , +IO_TREE_SELFTEST_TMP , +}; +struct extent_io_tree {struct rb_root state;struct btrfs_fs_info *fs_info;void *private_data;u64 dirty_bytes; -int track_uptodate; +bool track_uptodate; + +/* who owns this io tree, should be above IO_TREE_* enum */ +u8 owner; +spinlock_t lock;const struct extent_io_ops *ops; };
@@ -241,8 +256,9 @@ typedef struct extent_map *(get_extent_t)(struct btrfs_inode *inode, u64 start, u64 len, int create); -void extent_io_tree_init (struct btrfs_fs_info *fs_info, -struct extent_io_tree *tree,void *private_data); +void extent_io_tree_init (struct btrfs_fs_info *fs_info, +struct extent_io_tree *tree,unsigned int owner, +void *private_data);int try_release_extent_mapping (struct page *page,gfp_t mask);int try_release_extent_buffer (struct page *page); int lock_extent_bits(struct extent_io_tree *tree, u64 start, u64 end,
fs/btrfs/inode.c +4 -2
@@ -9128,8 +9128,10 @@ struct inode *btrfs_alloc_inode(struct super_block *sb) inode = &ei->vfs_inode;extent_map_tree_init (&ei->extent_tree); -extent_io_tree_init (fs_info, &ei->io_tree, inode); -extent_io_tree_init (fs_info, &ei->io_failure_tree, inode); +extent_io_tree_init (fs_info, &ei->io_tree,IO_TREE_INODE_IO_TREE , + inode); +extent_io_tree_init (fs_info, &ei->io_failure_tree, +IO_TREE_INODE_IO_FAILURE_TREE , inode); ei->io_tree.track_uptodate =1 ; ei->io_failure_tree.track_uptodate =1 ;atomic_set (&ei->sync_writers,0 );
fs/btrfs/relocation.c +2 -1
@@ -4175,7 +4175,8 @@ static struct reloc_control *alloc_reloc_control(struct btrfs_fs_info *fs_info)INIT_LIST_HEAD (&rc->reloc_roots);backref_cache_init (&rc->backref_cache);mapping_tree_init (&rc->reloc_root_tree); -extent_io_tree_init (fs_info, &rc->processed_blocks,NULL ); +extent_io_tree_init (fs_info, &rc->processed_blocks, +IO_TREE_RELOC_BLOCKS ,NULL );return rc; }
fs/btrfs/tests/btrfs-tests.c +4 -2
@@ -115,8 +115,10 @@ struct btrfs_fs_info *btrfs_alloc_dummy_fs_info(u32 nodesize, u32 sectorsize)INIT_LIST_HEAD (&fs_info->tree_mod_seq_list);INIT_RADIX_TREE (&fs_info->buffer_radix,GFP_ATOMIC );INIT_RADIX_TREE (&fs_info->fs_roots_radix,GFP_ATOMIC ); -extent_io_tree_init (fs_info, &fs_info->freed_extents[0 ],NULL ); -extent_io_tree_init (fs_info, &fs_info->freed_extents[1 ],NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[0 ], +IO_TREE_FS_INFO_FREED_EXTENTS0 ,NULL ); +extent_io_tree_init (fs_info, &fs_info->freed_extents[1 ], +IO_TREE_FS_INFO_FREED_EXTENTS1 ,NULL ); fs_info->pinned_extents = &fs_info->freed_extents[0 ];set_bit (BTRFS_FS_STATE_DUMMY_FS_INFO , &fs_info->fs_state);
fs/btrfs/tests/extent-io-tests.c +1 -1
@@ -77,7 +77,7 @@ static int test_find_delalloc(u32 sectorsize)return -ENOMEM ; } -extent_io_tree_init (NULL , &tmp,NULL ); +extent_io_tree_init (NULL , &tmp,IO_TREE_SELFTEST_TMP ,NULL );/* * First go through and create and mark all of our pages dirty, we pin
fs/btrfs/transaction.c +1 -1
@@ -274,7 +274,7 @@ static noinline int join_transaction(struct btrfs_fs_info *fs_info,spin_lock_init (&cur_trans->dropped_roots_lock);list_add_tail (&cur_trans->list, &fs_info->trans_list);extent_io_tree_init (fs_info, &cur_trans->dirty_pages, - fs_info->btree_inode); +IO_TREE_TRANSACTION_DIRTY_PAGES , fs_info->btree_inode); fs_info->generation++; cur_trans->transid = fs_info->generation; fs_info->running_transaction = cur_trans;
Signature · 1 line
2.21.0
Re: [PATCH v2 2/3] btrfs: Introduce extent_io_tree::owner to distinguish different io_trees
fs/btrfs/extent_io.h struct extent_io_ops { · line 118
Quoted 9 lines · Qu Wenruo
fs/btrfs/extent_io.h +9
-0+enum { +IO_TREE_FS_INFO_FREED_EXTENTS0 , +IO_TREE_FS_INFO_FREED_EXTENTS1 , +IO_TREE_INODE_IO_TREE , +IO_TREE_INODE_IO_FAILURE_TREE , +IO_TREE_RELOC_BLOCKS , +IO_TREE_TRANSACTION_DIRTY_PAGES , +IO_TREE_ROOT_DIRTY_LOG_PAGES , +IO_TREE_SELFTEST_TMP ,
Well, I guess that's always something that sounds like a pointless nitpicking but future code readers will complain, so allow me to complain now.
IO_TREE_INODE_IO_TREE repeats the 'IO_TREE', so my idea is do only IO_TREE_INODE_IO, similarly IO_TREE_INODE_IO_FAILURE.
And IO_TREE_SELFTEST, the 'TMP' part seems redundant.
Re: [PATCH v2 2/3] btrfs: Introduce extent_io_tree::owner to distinguish different io_trees
In reply to Qu Wenruofs/btrfs/extent_io.h struct extent_io_ops { · line 126
Quoted 7 lines · Qu Wenruo
struct
extent_io_tree{fs/btrfs/extent_io.h +1
-1struct rb_root state;struct btrfs_fs_info *fs_info;void *private_data;u64 dirty_bytes; -int track_uptodate; +bool track_uptodate;
Next time please do such change in a separate patch, I did that myself for now.
PATCH v2 3/3 btrfs: trace: Add trace events for extent_io_tree
In reply to Qu WenruoAlthough btrfs heavily relies on extent_io_tree, we don't really have any good trace events for them.
This patch will add the folowing trace events:trace_btrfs_set_extent_bit()trace_btrfs_clear_extent_bit()trace_btrfs_convert_extent_bit()
Since selftest could create temporary extent_io_tree without fs_info, modify TP_fast_assign_fsid() to accept NULL as fs_info. NULL fs_info will lead to all zero fsid.
The output would be:
btrfs_set_extent_bit: <FDID>: io_tree=IO_TREE ino=1 root=1 start=22036480 len=4096 set_bits=LOCKED
btrfs_set_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22040576 len=4096 set_bits=LOCKED
btrfs_set_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22044672 len=4096 set_bits=LOCKED
btrfs_set_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22048768 len=4096 set_bits=LOCKED
btrfs_clear_extent_bit: <FSID>: io_tree=IO_TREE ino=1 root=1 start=22036480 len=16384 clear_bits=LOCKED ^^^ Extent buffer 22036480 read from disc, the locking progress
btrfs_set_extent_bit: <FSID>: io_tree=TRANS_DIRTY_PAGES ino=1 root=1 start=30425088 len=16384 set_bits=DIRTY
btrfs_set_extent_bit: <FSID>: io_tree=TRANS_DIRTY_PAGES ino=1 root=1 start=30441472 len=16384 set_bits=DIRTY ^^^ 2 new tree blocks allocated in one transaction
btrfs_set_extent_bit: <FSID>: io_tree=FREED_EXTENTS0 ino=0 root=0 start=30523392 len=16384 set_bits=DIRTY
btrfs_set_extent_bit: <FSID>: io_tree=FREED_EXTENTS0 ino=0 root=0 start=30556160 len=16384 set_bits=DIRTY ^^^ 2 old tree blocks get pinned down
There is one point which need extra attention:
1) Those trace events are pretty heavy
The following workload would generate over 400 trace events.
mkfs.btrfs -f $dev
start_trace
mount $dev $mnt -o enospc_debug
sync
touch $mnt/file1
touch $mnt/file2
touch $mnt/file3
xfs_io -f -c "pwrite 0 16k" $mnt/file4
umount $mnt
end_trace
It's not recommended to use them in real world environment.
--- fs/btrfs/extent_io.c | 4 + include/trace/events/btrfs.h | 159 ++++++++++++++++++++++++++++++++++- 2 files changed, 162 insertions(+), 1 deletion(-)
fs/btrfs/extent_io.c +4 -0
@@ -582,6 +582,7 @@ int __clear_extent_bit(struct extent_io_tree *tree, u64 start, u64 end,int clear =0 ;btrfs_debug_check_extent_io_range (tree, start, end); +trace_btrfs_clear_extent_bit (tree, start, end - start +1 , bits);if (bits &EXTENT_DELALLOC ) bits |=EXTENT_NORESERVE ;
@@ -852,6 +853,7 @@ __set_extent_bit(struct extent_io_tree *tree, u64 start, u64 end,u64 last_end;btrfs_debug_check_extent_io_range (tree, start, end); +trace_btrfs_set_extent_bit (tree, start, end - start +1 , bits); bits |=EXTENT_FIRST_DELALLOC ; again:
@@ -1085,6 +1087,8 @@ int convert_extent_bit(struct extent_io_tree *tree, u64 start, u64 end,bool first_iteration = true;btrfs_debug_check_extent_io_range (tree, start, end); +trace_btrfs_convert_extent_bit (tree, start, end - start +1 , bits, + clear_bits); again:if (!prealloc) {
include/trace/events/btrfs.h +158 -1
187 lines not on this page · raw message
Signature · 1 line
2.21.0
include/trace/events/btrfs.h TRACE_DEFINE_ENUM(COMMIT_TRANS); · line 90
Quoted 10 lines · Qu Wenruo
include/trace/events/btrfs.h +10
-0+#define show_extent_io_tree_owner (owner) \ + __print_symbolic(owner, \ + { IO_TREE_FS_INFO_FREED_EXTENTS0, "FREED_EXTENTS0" }, \ + { IO_TREE_FS_INFO_FREED_EXTENTS1, "FREED_EXTENTS1" }, \ + { IO_TREE_INODE_IO_TREE, "IO_TREE" }, \ + { IO_TREE_INODE_IO_FAILURE_TREE, "IO_FAILURE_TREE" }, \ + { IO_TREE_RELOC_BLOCKS, "RELOCATION" }, \ + { IO_TREE_TRANSACTION_DIRTY_PAGES, "TRANS_DIRTY_PAGES" },\ + { IO_TREE_ROOT_DIRTY_LOG_PAGES, "ROOT_DIRTY_LOG" }, \ + { IO_TREE_SELFTEST_TMP, "SELFTEST_TMP" })
Additional to the previous patch, I think the point of the strings is to match the constants or at least be an exact substring. When I see a trace event I can simply copy&paste and search inside the sources if I'm interested. So in this case it would be without the IO_TREE_ prefix.
I'm going to update the patche as it's only a simple rename, no need to resend.
Quoted 7 lines · Qu Wenruo
- Allow NULL
fs_infoforTP_fast_assign_fsid()
There is extent bits operation in selftest which is too deep to passfs_info. And since it's in selftest, it shouldn't trigger trace events.
But to be safe, we still need to checkfs_indoinTP_fast_assign_fsid(), for NULLfs_info, just keep fsid filled with zero.
Ok, better be safe here. I'd still like to remove the conditional, as the tests typically access only a single filesystem we could export the fs_info globally, avoiding the need to pass it around.
Quoted 3 lines
There is one point which need extra attention:
1) Those trace events are pretty heavy
The following workload would generate over 400 trace events.
I'm not sure if 400 is considered a lot, I'd say 400.000 would be a lot for the steps below.
Quoted 12 lines
mkfs.btrfs -f $dev
start_trace
mount $dev $mnt -oenospc_debug
sync
touch $mnt/file1
touch $mnt/file2
touch $mnt/file3
xfs_io-f -c "pwrite 0 16k" $mnt/file4 umount $mnt
end_trace
It's not recommended to use them in real world environment.
Quoted 7 lines
Changelog:
v2:
- Introducefs_infoto distinguish different btrfs filesystems
- Code style change to make trace code more elegant
- Minor IO_TREE_* naming change.
- Usebtrfs_ino()to replace raw inode number.
- Changeextent_io_tree::ownerdeclaration to avoid affecting spinlock.
v2 looks good to me, thanks. I'll add it to the 5.2 queue.
Quoted 9 lines · David Sterba
Quoted 7 lines · Qu Wenruo
- Allow NULL
fs_infoforTP_fast_assign_fsid()
There is extent bits operation in selftest which is too deep to passfs_info. And since it's in selftest, it shouldn't trigger trace events.
But to be safe, we still need to checkfs_indoinTP_fast_assign_fsid(), for NULLfs_info, just keep fsid filled with zero.
Quoted 3 lines
Ok, better be safe here. I'd still like to remove the conditional, as the tests typically access only a single filesystem we could export the
fs_infoglobally, avoiding the need to pass it around.
In fact, it's purely to be safe here.
Since the selftest is only executed at module load time, it's pretty hard to enable trace event at that small time windows. And if btrfs is complied into kernel, it's definitely impossible.
Quoted 7 lines
Quoted 4 lines
There is one point which need extra attention:
1) Those trace events are pretty heavy
The following workload would generate over 400 trace events.I'm not sure if 400 is considered a lot, I'd say 400.000 would be a lot for the steps below.
Considering other btrfs events are hardly to hit 40 for that small workload, among btrfs specific events, it looks a little heavy.
Quoted 21 lines
Quoted 13 lines
mkfs.btrfs -f $dev
start_trace
mount $dev $mnt -oenospc_debug
sync
touch $mnt/file1
touch $mnt/file2
touch $mnt/file3
xfs_io-f -c "pwrite 0 16k" $mnt/file4 umount $mnt
end_trace
It's not recommended to use them in real world environment.Quoted 7 lines
Changelog:
v2:
- Introducefs_infoto distinguish different btrfs filesystems
- Code style change to make trace code more elegant
- Minor IO_TREE_* naming change.
- Usebtrfs_ino()to replace raw inode number.
- Changeextent_io_tree::ownerdeclaration to avoid affecting spinlock.
Quoted 2 lines
v2 looks good to me, thanks. I'll add it to the 5.2 queue.
Thanks for merging and update it for the renaming.
Thanks,
Qu