From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] btrfs: move some features out of experimental
Date: Mon, 16 Mar 2026 09:58:10 +0100 [thread overview]
Message-ID: <20260316085810.GO5735@suse.cz> (raw)
In-Reply-To: <a19ad870-a52a-4e26-8ac7-cfabfb4a5e4b@suse.com>
On Wed, Mar 04, 2026 at 02:34:32PM +1030, Qu Wenruo wrote:
> > Adding all of them at once feels a bit risky. I don't think that it has
> > enough exposure and testing because of number of the possible
> > combinations.
> >
> > The shutdown is orthogonal to the rest so this can be enabled by
> > default.
>
> So can I add that shutdown one into for-next branch?
Yes please.
> > For the rest the bs/ps is namely an ARM thing with the 64K
> > pages,
>
> Thus I'd say it shouldn't affect most end users (if any).
AFAIK the 64K pages are used on big machines with lots of memory and the
support for 64K/4K combinations was needed for interoperability. Yes
there are users.
next prev parent reply other threads:[~2026-03-16 8:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 3:33 [PATCH v2 0/4] btrfs: move some features out of experimental Qu Wenruo
2026-02-27 3:33 ` [PATCH v2 1/4] btrfs: drop 2K block size support Qu Wenruo
2026-03-04 3:48 ` David Sterba
2026-03-04 3:51 ` Qu Wenruo
2026-02-27 3:33 ` [PATCH v2 2/4] btrfs: move shutdown and remove_bdev callbacks out of experimental features Qu Wenruo
2026-02-27 3:33 ` [PATCH v2 3/4] btrfs: move larger data folios " Qu Wenruo
2026-03-10 6:43 ` kernel test robot
2026-03-10 7:03 ` Qu Wenruo
2026-03-10 7:21 ` Oliver Sang
2026-03-10 7:58 ` Qu Wenruo
2026-03-11 13:38 ` Oliver Sang
2026-02-27 3:33 ` [PATCH v2 4/4] btrfs: move block size < page size support " Qu Wenruo
2026-03-04 3:57 ` [PATCH v2 0/4] btrfs: move some features out of experimental David Sterba
2026-03-04 4:04 ` Qu Wenruo
2026-03-16 8:58 ` David Sterba [this message]
2026-03-16 9:16 ` 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=20260316085810.GO5735@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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