From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v4 0/5] btrfs: data block group size classes
Date: Thu, 15 Dec 2022 16:06:30 -0800 [thread overview]
Message-ID: <cover.1671149056.git.boris@bur.io> (raw)
This patch set introduces the notion of size classes to the block group
allocator for data block groups. This is specifically useful because the
first fit allocator tends to perform poorly when large extents free up
in older block groups and small writes suddenly shift there. Generally,
it should lead to slightly more predictable allocator behavior as the
gaps left by frees will be used by allocations of a similar size.
Details about the changes and performance testing are in the individual
commit messages.
The last two patches constitute the business of the change. One adds the
size classes and the other handles the fact that we don't want to
persist the size class, so we don't know it when we first load a block
group.
The final patch is a tweak to skip zoned fs-es which is particularly
meaningful for ZNS.
---
v4:
- add patch to skip zoned fs
v3:
- fix double newline in extent-tree.h
- fix ctree.h include in extent-tree.h refactor
v2:
- removed 1G falloc extents patch
- rebased tracepoints patches onto significant header file refactor
Boris Burkov (5):
btrfs: use ffe_ctl in btrfs allocator tracepoints
btrfs: add more ffe tracepoints
btrfs: introduce size class to block group allocator
btrfs: load block group size class when caching
btrfs: dont use size classes for zoned file systems
fs/btrfs/block-group.c | 243 ++++++++++++++++++++++++++++++++---
fs/btrfs/block-group.h | 16 ++-
fs/btrfs/extent-tree.c | 167 +++++++-----------------
fs/btrfs/extent-tree.h | 81 ++++++++++++
fs/btrfs/super.c | 1 +
fs/btrfs/zoned.c | 2 +
include/trace/events/btrfs.h | 128 ++++++++++++++----
7 files changed, 479 insertions(+), 159 deletions(-)
--
2.38.1
next reply other threads:[~2022-12-16 0:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 0:06 Boris Burkov [this message]
2022-12-16 0:06 ` [PATCH v4 1/5] btrfs: use ffe_ctl in btrfs allocator tracepoints Boris Burkov
2022-12-16 0:06 ` [PATCH v4 2/5] btrfs: add more ffe tracepoints Boris Burkov
2022-12-16 0:06 ` [PATCH v4 3/5] btrfs: introduce size class to block group allocator Boris Burkov
2023-01-13 9:55 ` Johannes Thumshirn
2022-12-16 0:06 ` [PATCH v4 4/5] btrfs: load block group size class when caching Boris Burkov
2022-12-16 8:07 ` kernel test robot
2022-12-16 0:06 ` [PATCH v4 5/5] btrfs: dont use size classes for zoned file systems Boris Burkov
2022-12-16 5:35 ` kernel test robot
2022-12-16 6:06 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1671149056.git.boris@bur.io \
--to=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox