From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/6] btrfs: prepare for larger folios support
Date: Mon, 10 Mar 2025 18:05:56 +1030 [thread overview]
Message-ID: <cover.1741591823.git.wqu@suse.com> (raw)
[CHANGELOG]
v2:
- Split the subpage.[ch] modification into 3 patches
- Rebased the latest for-next branch
Now all dependency are in for-next.
This means:
- Our subpage routine should check against the folio size other than
PAGE_SIZE
- Make functions handling filemap folios to use folio_size() other than
PAGE_SIZE
The most common paths are:
* Buffered reads/writes
* Uncompressed folio writeback
Already handled pretty well
* Compressed read
* Compressed write
To take full advantage of larger folios, we should use folio_iter
other than bvec_iter.
This will be a dedicated patchset, and the existing bvec_iter can
still handle larger folios.
Internal usages can still use page sized folios, or even pages,
including:
* Encoded reads/writes
* Compressed folios
* RAID56 internal pages
* Scrub internal pages
This patchset will handle the above mentioned points by:
- Prepare the subpage routine to handle larger folios
This will introduce a small overhead, as all checks are against folio
sizes, even on x86_64 we can no longer skip subpage completely.
This is done in the first patch.
- Convert straightforward PAGE_SIZE users to use folio_size()
This is done in the remaining patches.
Currently this patchset is not a exhaustive conversion, I'm pretty sure
there are other complex situations which can cause problems.
Those problems can only be exposed and fixed after switching on the
experimental larger folios support later.
Qu Wenruo (6):
btrfs: subpage: make btrfs_is_subpage() check against a folio
btrfs: add a @fsize parameter to btrfs_alloc_subpage()
btrfs: replace PAGE_SIZE with folio_size for subpage.[ch]
btrfs: prepare btrfs_launcher_folio() for larger folios support
btrfs: prepare extent_io.c for future larger folio support
btrfs: prepare btrfs_page_mkwrite() for larger folios
fs/btrfs/extent_io.c | 49 ++++++++++++++++++++++++--------------------
fs/btrfs/file.c | 19 +++++++++--------
fs/btrfs/inode.c | 4 ++--
fs/btrfs/subpage.c | 38 +++++++++++++++++-----------------
fs/btrfs/subpage.h | 16 +++++++--------
5 files changed, 66 insertions(+), 60 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-10 7:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:35 Qu Wenruo [this message]
2025-03-10 7:35 ` [PATCH 1/6] btrfs: subpage: make btrfs_is_subpage() check against a folio Qu Wenruo
2025-03-10 7:35 ` [PATCH 2/6] btrfs: add a @fsize parameter to btrfs_alloc_subpage() Qu Wenruo
2025-03-10 7:35 ` [PATCH 3/6] btrfs: replace PAGE_SIZE with folio_size for subpage.[ch] Qu Wenruo
2025-03-10 7:36 ` [PATCH 4/6] btrfs: prepare btrfs_launcher_folio() for larger folios support Qu Wenruo
2025-03-10 7:36 ` [PATCH 5/6] btrfs: prepare extent_io.c for future larger folio support Qu Wenruo
2025-03-10 23:27 ` Boris Burkov
2025-03-10 23:51 ` Qu Wenruo
2025-03-10 7:36 ` [PATCH 6/6] btrfs: prepare btrfs_page_mkwrite() for larger folios Qu Wenruo
2025-03-10 23:32 ` [PATCH v2 0/6] btrfs: prepare for larger folios support Boris Burkov
2025-03-10 23:56 ` Qu Wenruo
2025-03-11 10:25 ` Johannes Thumshirn
2025-03-12 13:44 ` David Sterba
2025-03-13 15:21 ` Nathan Chancellor
2025-03-13 20:50 ` 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.1741591823.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