From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/4] btrfs: allow creating inline data extents for sector size < page size case
Date: Sat, 15 Feb 2025 19:04:18 +1030 [thread overview]
Message-ID: <cover.1739608189.git.wqu@suse.com> (raw)
[CHANGELOG]
v2:
- Add the previous inline read fix into the series
- Add a patch to remove the subpage experimental warning message
The main reason for the warning is the lack of some features, but it's
no longer the case.
For btrfs block size < page size (subpage), there used to a list of
features that are not supported:
- RAID56
Added in v5.19
- Block perfect compressed write
Added in v6.13, previously only page aligned range can go through
compressed write path.
- Inline data extent creation
But now the only feature that is missing is only inline data extent
creation.
And all technical problems are solved in v6.13, it's time for us to
allow subpage btrfs to create inline data extents.
The first patch is to fix a bug that can only be triggered with recent
partial uptodate folio support.
The second patch fixes a minor issue for qgroup accounting for inlined
data extents.
The third path enables inline data extent creation for subpage btrfs.
And finally remove the experimental warning message for subpage btrfs.
Qu Wenruo (4):
btrfs: fix inline data extent reads which zero out the remaining part
btrfs: fix the qgroup data free range for inline data extents
btrfs: allow inline data extents creation if sector size < page size
btrfs: remove the subpage related warning message
fs/btrfs/disk-io.c | 5 -----
fs/btrfs/inode.c | 30 ++++++++++--------------------
2 files changed, 10 insertions(+), 25 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-15 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 8:34 Qu Wenruo [this message]
2025-02-15 8:34 ` [PATCH v2 1/4] btrfs: fix inline data extent reads which zero out the remaining part Qu Wenruo
2025-02-21 12:32 ` Filipe Manana
2025-02-21 22:39 ` Qu Wenruo
2025-02-24 16:47 ` Filipe Manana
2025-02-27 14:36 ` Daniel Vacek
2025-02-27 23:39 ` Qu Wenruo
2025-03-06 9:24 ` David Sterba
2025-02-15 8:34 ` [PATCH v2 2/4] btrfs: fix the qgroup data free range for inline data extents Qu Wenruo
2025-02-15 8:34 ` [PATCH v2 3/4] btrfs: allow inline data extents creation if sector size < page size Qu Wenruo
2025-02-15 8:34 ` [PATCH v2 4/4] btrfs: remove the subpage related warning message Qu Wenruo
2025-02-15 14:42 ` [PATCH v2 0/4] btrfs: allow creating inline data extents for sector size < page size case Neal Gompa
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.1739608189.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