From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/4] btrfs: bs > ps support preparation
Date: Mon, 1 Sep 2025 14:54:02 +0930 [thread overview]
Message-ID: <cover.1756703958.git.wqu@suse.com> (raw)
Some extra small and safe bs > ps support preparation, mostly focusing
on the bio vec iteration code and cached order/bit members.
This time the difference is, I can enable some early local bs > ps
tests, so basic file read/write and csum verification are all done
properly.
The tricky part is still inside the compression, and maybe some other
functionalities.
Qu Wenruo (4):
btrfs: support all block sizes which is no larger than page size
btrfs: cache max and min order inside btrfs_fs_info
btrfs: replace single page bio_iter_iovec() usage
btrfs: replace bio_for_each_segment usage
fs/btrfs/bio.c | 3 ++-
fs/btrfs/btrfs_inode.h | 6 +++---
fs/btrfs/compression.c | 3 +--
fs/btrfs/disk-io.c | 2 ++
fs/btrfs/file-item.c | 13 +++++++------
fs/btrfs/fs.c | 4 ++++
fs/btrfs/fs.h | 8 +++++---
fs/btrfs/raid56.c | 10 +++++-----
8 files changed, 29 insertions(+), 20 deletions(-)
--
2.50.1
next reply other threads:[~2025-09-01 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 5:24 Qu Wenruo [this message]
2025-09-01 5:24 ` [PATCH 1/4] btrfs: support all block sizes which is no larger than page size Qu Wenruo
2025-09-01 5:24 ` [PATCH 2/4] btrfs: cache max and min order inside btrfs_fs_info Qu Wenruo
2025-09-01 18:10 ` David Sterba
2025-09-02 3:46 ` kernel test robot
2025-09-01 5:24 ` [PATCH 3/4] btrfs: replace single page bio_iter_iovec() usage Qu Wenruo
2025-09-01 6:25 ` Qu Wenruo
2025-09-01 5:24 ` [PATCH 4/4] btrfs: replace bio_for_each_segment usage Qu Wenruo
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.1756703958.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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.