public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/4] btrfs: move some features out of experimental
Date: Fri, 27 Feb 2026 14:03:42 +1030	[thread overview]
Message-ID: <cover.1772162871.git.wqu@suse.com> (raw)

[CHANGELOG]
v2:
- Move bs < ps && bs != 4K out of experimental
  That feature is a pretty small niche though.
  The basis is already there from the bs < ps support for a while.

- Remove 2K block size support
  That is too niche, considering how easy to trigger subpage routine
  with the larger data folio support, there is not much need for it.

The following features can be moved out of experimental in v7.1:

- Large data folios
  It's introduced in v6.17, but we still have a bug fix related for it
  in v6.19.
  If there is no new bug exposed I believe it's time to expose this
  feature to end users.

- Shutdown and remove_bdev callbacks
  It's introduced in v6.19, but there is no major known bug exposed yet.
  Furthermore the remove_bdev callback, aka auto-shutdown/degradation
  when a device is missing, can affect end users.

  Thus we want some feedbacks from early adopters.

- Block size smaller than page size but not 4K support
  The requirement for 4K block size is purely artificial to reduce our
  test load.
  But since we're moving towards supporting all block sizes, the
  artifical limit can be lifted now.

Qu Wenruo (4):
  btrfs: drop 2K block size support
  btrfs: move shutdown and remove_bdev callbacks out of experimental
    features
  btrfs: move larger data folios out of experimental features
  btrfs: move block size < page size support out of experimental
    features

 fs/btrfs/Kconfig       |  4 +---
 fs/btrfs/btrfs_inode.h |  2 --
 fs/btrfs/fs.c          | 16 ++++------------
 fs/btrfs/fs.h          | 11 +----------
 fs/btrfs/super.c       |  4 ----
 5 files changed, 6 insertions(+), 31 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-02-27  3:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  3:33 Qu Wenruo [this message]
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
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=cover.1772162871.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