From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: enable full bs <= ps support
Date: Fri, 19 Jun 2026 18:24:45 +0930 [thread overview]
Message-ID: <cover.1781859111.git.wqu@suse.com> (raw)
Btrfs has supported block size < page size for a while, but that is only
when the block size is 4K.
So for 64K page size, 8K/16K/32K block sizes are not supported no matter
what.
That's is completely an artificial limit, introduced just to reduce our
test workload.
But after all these years, we even have experimental bs > ps support
now.
There is really no reason not to support the extra block sizes.
The first patch is a small comment update.
The second one introduces the real change.
Qu Wenruo (2):
btrfs: remove the out-of-date comments on the 2K block size
btrfs: allow any block size that is no larger than page size
fs/btrfs/fs.c | 19 ++++---------------
1 file changed, 4 insertions(+), 15 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-19 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 8:54 Qu Wenruo [this message]
2026-06-19 8:54 ` [PATCH 1/2] btrfs: remove the out-of-date comments on the 2K block size Qu Wenruo
2026-06-19 9:04 ` Johannes Thumshirn
2026-06-19 8:54 ` [PATCH 2/2] btrfs: allow any block size that is no larger than page size Qu Wenruo
2026-06-19 9:08 ` Johannes Thumshirn
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.1781859111.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.