From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: migrate the remaining functions exposed by a full fstests with larger metadata folios
Date: Tue, 12 Dec 2023 15:54:08 +1030 [thread overview]
Message-ID: <cover.1702354716.git.wqu@suse.com> (raw)
[REPO]
This patchset along with all the previous migrations (and the final
enablement patch) can be found here:
https://github.com/adam900710/linux/tree/eb_memory
With all the previous migrations (although only tested without larger
folios), we are finally just one step away from enabling larger folio
support for btrfs metadata.
During my local full fstests runs with larger metadata folios, there are
only two bugs hit, all related to some code path not yet handling folios
correct:
- eb_bitmap_offset()
- btrfs_repair_eb_io_failure()
Otherwise my local branch can already pass local fstests without new
regressions.
So here is the final (and I hope is the last) migrations for involed
metadata code path, before the final patch enabling larger folio
support.
Qu Wenruo (2):
btrfs: migrate eb_bitmap_offset() to folio interfaces
btrfs: migrate btrfs_repair_io_failure() to folio interfaces
fs/btrfs/bio.c | 15 +++++++++++----
fs/btrfs/bio.h | 4 ++--
fs/btrfs/disk-io.c | 13 +++++++------
fs/btrfs/extent_io.c | 22 ++++++++++------------
4 files changed, 30 insertions(+), 24 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-12 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 5:24 Qu Wenruo [this message]
2023-12-12 5:24 ` [PATCH 1/2] btrfs: migrate eb_bitmap_offset() to folio interfaces Qu Wenruo
2023-12-12 5:24 ` [PATCH 2/2] btrfs: migrate btrfs_repair_io_failure() " Qu Wenruo
2023-12-13 22:39 ` [PATCH 0/2] btrfs: migrate the remaining functions exposed by a full fstests with larger metadata folios 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.1702354716.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