diff options
| author | Nikolay Borisov <[email protected]> | 2022-06-17 12:53:34 +0000 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2022-07-25 15:45:37 +0000 |
| commit | 1f4f639fe729bcfe097fa6c2305eea664110bf6a (patch) | |
| tree | b85187ae7385acc7e0dbfd4f8818120553ae002b /fs/btrfs/ordered-data.c | |
| parent | btrfs: warn about dev extents that are inside the reserved range (diff) | |
| download | kernel-1f4f639fe729bcfe097fa6c2305eea664110bf6a.tar.gz kernel-1f4f639fe729bcfe097fa6c2305eea664110bf6a.zip | |
btrfs: batch up release of reserved metadata for delayed items used for deletion
With Filipe's recent rework of the delayed inode code one aspect which
isn't batched is the release of the reserved metadata of delayed inode's
delete items. With this patch on top of Filipe's rework and running the
same test as provided in the description of a patch titled
"btrfs: improve batch deletion of delayed dir index items" I observe
the following change of the number of calls to btrfs_block_rsv_release:
Before this change:
- block_rsv_release: 1004
- btrfs_delete_delayed_items_total_time: 14602
- delete_batches: 505
After:
- block_rsv_release: 510
- btrfs_delete_delayed_items_total_time: 13643
- delete_batches: 507
Reviewed-by: Filipe Manana <[email protected]>
Signed-off-by: Nikolay Borisov <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'fs/btrfs/ordered-data.c')
0 files changed, 0 insertions, 0 deletions