From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: enable large folios for data reloc inodes
Date: Thu, 17 Jul 2025 06:44:56 +0930 [thread overview]
Message-ID: <cover.1752700452.git.wqu@suse.com> (raw)
Although large data folios are enabled for experimental builds, data
reloc inodes are excluded due to the cluster folio handling are still
done in fixed page size.
But data reloc inodes fit large folios better than regular inodes, as
each relocation cluster is one or more file extents that are contiguous
in their logical addresses.
This series will enable large folios for data reloc inodes by:
- Simplify the handling of cluster boundary folio invalidation
This patch has been sent to the list already, but it's the dependency
of the series.
- Enhance the output of btrfs_subpage_assert()
As it easily caught a lot of bugs in the relocation code that are
still using PAGE_SIZE
- Enable large folios for data reloc inodes
The last patch that remove the PAGE_SIZE usage and fixed PAGE_SIZE
itearation of data reloc inodes.
Qu Wenruo (3):
btrfs: reloc: unconditionally invalidate the page cache for each
cluster
btrfs: output more info when btrfs_subpage_assert() failed
btrfs: enable large data folios for data reloc inode
fs/btrfs/btrfs_inode.h | 4 ---
fs/btrfs/relocation.c | 82 +++++++++++-------------------------------
fs/btrfs/subpage.c | 5 +--
3 files changed, 24 insertions(+), 67 deletions(-)
--
2.50.0
next reply other threads:[~2025-07-16 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 21:14 Qu Wenruo [this message]
2025-07-16 21:14 ` [PATCH 1/3] btrfs: reloc: unconditionally invalidate the page cache for each cluster Qu Wenruo
2025-07-16 21:14 ` [PATCH 2/3] btrfs: output more info when btrfs_subpage_assert() failed Qu Wenruo
2025-07-16 21:14 ` [PATCH 3/3] btrfs: enable large data folios for data reloc inode 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.1752700452.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