From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] btrfs: cleanup and small refactors around __btrfs_map_block()
Date: Fri, 17 Feb 2023 13:36:57 +0800 [thread overview]
Message-ID: <cover.1676611535.git.wqu@suse.com> (raw)
This series is based on the current misc-next branch, and can be fetched
from github:
https://github.com/adam900710/linux/tree/map_block_refactor
This is the rebased and merged version of two patchset:
btrfs: reduce div64 calls for __btrfs_map_block() and its variants
btrfs: reduce the memory usage for btrfs_io_context, and reduce its variable sized members
Originally the 2nd patchset has some dependency on the first one, but
the first one is causing some conflicts with newer cleanups, thus only
the 2nd patchset get merged into for-next.
This updated version would resolve the conflicts, and use the modified
version from for-next.
Qu Wenruo (6):
btrfs: remove map_lookup->stripe_len
btrfs: reduce div64 calls by limiting the number of stripes of a chunk
to u32
btrfs: simplify the bioc argument for handle_ops_on_dev_replace()
btrfs: reduce type width of btrfs_io_contexts
btrfs: use a more space efficient way to represent the source of
duplicated stripes
btrfs: replace btrfs_io_context::raid_map with a fixed u64 value
fs/btrfs/block-group.c | 22 +-
fs/btrfs/raid56.c | 68 ++++--
fs/btrfs/scrub.c | 85 +++----
fs/btrfs/tests/extent-map-tests.c | 1 -
fs/btrfs/tree-checker.c | 14 ++
fs/btrfs/volumes.c | 385 ++++++++++++++----------------
fs/btrfs/volumes.h | 79 +++++-
include/trace/events/btrfs.h | 2 +-
8 files changed, 362 insertions(+), 294 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-17 5:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 5:36 Qu Wenruo [this message]
2023-02-17 5:36 ` [PATCH 1/6] btrfs: remove map_lookup->stripe_len Qu Wenruo
2023-02-17 5:36 ` [PATCH 2/6] btrfs: reduce div64 calls by limiting the number of stripes of a chunk to u32 Qu Wenruo
2023-02-20 21:05 ` David Sterba
2023-02-17 5:37 ` [PATCH 3/6] btrfs: simplify the bioc argument for handle_ops_on_dev_replace() Qu Wenruo
2023-02-17 5:37 ` [PATCH 4/6] btrfs: reduce type width of btrfs_io_contexts Qu Wenruo
2023-02-17 5:37 ` [PATCH 5/6] btrfs: use a more space efficient way to represent the source of duplicated stripes Qu Wenruo
2023-02-17 5:37 ` [PATCH 6/6] btrfs: replace btrfs_io_context::raid_map with a fixed u64 value Qu Wenruo
2023-02-20 21:08 ` [PATCH 0/6] btrfs: cleanup and small refactors around __btrfs_map_block() 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.1676611535.git.wqu@suse.com \
--to=wqu@suse.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;
as well as URLs for NNTP newsgroup(s).