summaryrefslogtreecommitdiff
path: root/fs/btrfs/extent-tree.c
diff options
context:
space:
mode:
authorNaohiro Aota <naohiro.aota@wdc.com>2023-08-08 01:12:40 +0900
committerDavid Sterba <dsterba@suse.com>2023-08-21 14:52:19 +0200
commit5b135b382a360f4c87cf8896d1465b0b07f10cb0 (patch)
tree5063c0460bc9158d468f2274e9dce9e4ac69f25c /fs/btrfs/extent-tree.c
parent5a7d107e5ef9b452cf0aa96ac931b29ea980d997 (diff)
downloadlinux-5b135b382a360f4c87cf8896d1465b0b07f10cb0.tar.gz
linux-5b135b382a360f4c87cf8896d1465b0b07f10cb0.tar.bz2
linux-5b135b382a360f4c87cf8896d1465b0b07f10cb0.zip
btrfs: zoned: re-enable metadata over-commit for zoned mode
Now that, we can re-enable metadata over-commit. As we moved the activation from the reservation time to the write time, we no longer need to ensure all the reserved bytes is properly activated. Without the metadata over-commit, it suffers from lower performance because it needs to flush the delalloc items more often and allocate more block groups. Re-enabling metadata over-commit will solve the issue. Fixes: 79417d040f4f ("btrfs: zoned: disable metadata overcommit for zoned") CC: stable@vger.kernel.org # 6.1+ Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/extent-tree.c')
0 files changed, 0 insertions, 0 deletions