From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/5] btrfs: data block group size classes
Date: Wed, 5 Oct 2022 12:49:17 -0700 [thread overview]
Message-ID: <cover.1664999303.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.
Boris Burkov (5):
btrfs: 1G falloc extents
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
fs/btrfs/block-group.c | 234 ++++++++++++++++++++++++++++++++---
fs/btrfs/block-group.h | 15 ++-
fs/btrfs/extent-tree.c | 166 +++++++------------------
fs/btrfs/extent-tree.h | 86 +++++++++++++
fs/btrfs/inode.c | 2 +-
fs/btrfs/super.c | 1 +
include/trace/events/btrfs.h | 128 +++++++++++++++----
7 files changed, 472 insertions(+), 160 deletions(-)
create mode 100644 fs/btrfs/extent-tree.h
--
2.37.2
next reply other threads:[~2022-10-05 19:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:49 Boris Burkov [this message]
2022-10-05 19:49 ` [PATCH 1/5] btrfs: 1G falloc extents Boris Burkov
2022-10-06 7:37 ` Qu Wenruo
2022-10-06 9:48 ` Filipe Manana
2022-10-06 18:38 ` Boris Burkov
2022-10-06 19:56 ` Filipe Manana
2022-10-06 20:41 ` Boris Burkov
2022-10-06 23:03 ` Qu Wenruo
2022-10-06 8:48 ` Johannes Thumshirn
2022-10-07 3:23 ` Wang Yugui
2022-10-07 3:29 ` Qu Wenruo
2022-10-07 3:40 ` Qu Wenruo
2022-10-05 19:49 ` [PATCH 2/5] btrfs: use ffe_ctl in btrfs allocator tracepoints Boris Burkov
2022-10-11 13:03 ` David Sterba
2022-10-14 12:22 ` David Sterba
2022-10-05 19:49 ` [PATCH 3/5] btrfs: add more ffe tracepoints Boris Burkov
2022-10-05 19:49 ` [PATCH 4/5] btrfs: introduce size class to block group allocator Boris Burkov
2022-10-05 19:49 ` [PATCH 5/5] btrfs: load block group size class when caching Boris Burkov
2022-10-06 6:02 ` kernel test robot
2022-10-06 7:31 ` kernel test robot
2022-10-06 8:13 ` kernel test robot
2022-10-11 13:06 ` [PATCH 0/5] btrfs: data block group size classes David Sterba
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.1664999303.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.