From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs: migrate extent_buffer::pages[] to folio and more cleanups
Date: Fri, 1 Dec 2023 16:36:53 +1030 [thread overview]
Message-ID: <cover.1701410200.git.wqu@suse.com> (raw)
[CHANGELOG]
v2:
- Adda new patch to do more cleanups for metadata page pointers usage
This patchset would migrate extent_buffer::pages[] to folios[], then
cleanup the existing metadata page pointer usage to proper folios ones.
This cleanup would help future higher order folios usage for metadata in
the following aspects:
- No more need to iterate through the remaining pages for page flags
We just call folio_set/mark/start_*() helpers, for the single folio.
The helper would only set the flag (mostly for the leading page).
- Single bio_add_folio() call for the whole eb
- Better filio helpers naming
PageUptodate() compared to folio_test_uptodate().
The first patch would do a very simple conversion, then the 2nd patch do
the prepartion for the higher order folio situation.
There are two locations which won't be converted to folios yet:
- Subpage code
There is no meaning to support higher order folio for subpage.
The two conditions are just conflicting with each other.
- Data page pointers
That would be more useful in the future, before we going to support
multi-page sectorsize.
However the 2nd one would also add a new corner case:
- Order mismatch in filemap and eb folios
Unforatunately I don't have a better plan other than re-allocate the
folios to the same order.
Maybe in the future we would have better ways to handle it? Like
migrating the pages to the higher order one?
Qu Wenruo (2):
btrfs: migrate extent_buffer::pages[] to folio
btrfs: cleanup metadata page pointer usage
fs/btrfs/accessors.c | 20 +-
fs/btrfs/accessors.h | 4 +-
fs/btrfs/ctree.c | 2 +-
fs/btrfs/disk-io.c | 25 +-
fs/btrfs/extent_io.c | 402 ++++++++++++++++++-------------
fs/btrfs/extent_io.h | 21 +-
fs/btrfs/inode.c | 2 +-
fs/btrfs/subpage.c | 60 ++---
fs/btrfs/subpage.h | 11 +-
fs/btrfs/tests/extent-io-tests.c | 4 +-
10 files changed, 322 insertions(+), 229 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-01 6:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 6:06 Qu Wenruo [this message]
2023-12-01 6:06 ` [PATCH v2 1/2] btrfs: migrate extent_buffer::pages[] to folio Qu Wenruo
2023-12-01 6:06 ` [PATCH v2 2/2] btrfs: cleanup metadata page pointer usage Qu Wenruo
2023-12-05 14:00 ` David Sterba
2023-12-05 20:13 ` Qu Wenruo
2023-12-04 16:26 ` [PATCH v2 0/2] btrfs: migrate extent_buffer::pages[] to folio and more cleanups David Sterba
2023-12-04 21:10 ` Qu Wenruo
2023-12-05 14:04 ` 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.1701410200.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