summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/block-group.h
diff options
context:
space:
mode:
authorBoris Burkov <boris@bur.io>2022-12-15 16:06:35 -0800
committerDavid Sterba <dsterba@suse.com>2023-02-13 17:50:34 +0100
commitcb0922f264643f03b04352f7a04abb913c609369 (patch)
tree2fbe7804f1e87b4e080b5c5a83575cd8011642e4 /fs/btrfs/block-group.h
parentc7eec3d9aa955cbd00470f874f34bdba946bd101 (diff)
downloadlinux-stable-cb0922f264643f03b04352f7a04abb913c609369.tar.gz
linux-stable-cb0922f264643f03b04352f7a04abb913c609369.tar.bz2
linux-stable-cb0922f264643f03b04352f7a04abb913c609369.zip
btrfs: don't use size classes for zoned file systems
When a file system has ZNS devices which are constrained by a maximum number of active block groups, then not being able to use all the block groups for every allocation is not ideal, and could cause us to loop a ton with mixed size allocations. In general, since zoned doesn't write into gaps behind where block groups are writing, it is not susceptible to the same sort of fragmentation that size classes are designed to solve, so we can skip size classes for zoned file systems in general, even though there would probably be no harm for SMR devices. Signed-off-by: Boris Burkov <boris@bur.io> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/block-group.h')
-rw-r--r--fs/btrfs/block-group.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/btrfs/block-group.h b/fs/btrfs/block-group.h
index 2b9d328b589e..4fdc39f00a4d 100644
--- a/fs/btrfs/block-group.h
+++ b/fs/btrfs/block-group.h
@@ -363,5 +363,6 @@ enum btrfs_block_group_size_class btrfs_calc_block_group_size_class(u64 size);
int btrfs_use_block_group_size_class(struct btrfs_block_group *bg,
enum btrfs_block_group_size_class size_class,
bool force_wrong_size_class);
+bool btrfs_block_group_should_use_size_class(struct btrfs_block_group *bg);
#endif /* BTRFS_BLOCK_GROUP_H */