Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: split out CONFIG_BTRFS_EXPERIMENTAL from CONFIG_BTRFS_DEBUG
Date: Mon, 16 Sep 2024 18:35:27 +0930	[thread overview]
Message-ID: <cover.1726477365.git.wqu@suse.com> (raw)

The first patch is to make it more consistent for assert_rbio() to
follow the CONFIG_BTRFS_ASSERT.

Then the second patch split out the following features into the new
CONFIG_BTRFS_EXPERIMENTAL:

- Extent map shrinker
- Extent tree v2
- Raid stripe tree
- Csum offload mode
- Send string v3

This is mostly to make those features to get more attention, and
eventually to move into stable features.

So far I think csum offload mode and extent map shrinker are strong
candidates, and later sector perfect compression will also join the
experimental features.

Qu Wenruo (2):
  btrfs: make assert_rbio() to only check CONFIG_BTRFS_DEBUG
  btrfs: split out CONFIG_BTRFS_EXPERIMENTAL from CONFIG_BTRFS_DEBUG

 fs/btrfs/Kconfig   | 9 +++++++++
 fs/btrfs/bio.c     | 2 +-
 fs/btrfs/fs.h      | 4 ++--
 fs/btrfs/raid56.c  | 3 +--
 fs/btrfs/send.h    | 2 +-
 fs/btrfs/super.c   | 6 +++---
 fs/btrfs/sysfs.c   | 4 ++--
 fs/btrfs/volumes.h | 4 ++--
 8 files changed, 21 insertions(+), 13 deletions(-)

-- 
2.46.0


             reply	other threads:[~2024-09-16  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  9:05 Qu Wenruo [this message]
2024-09-16  9:05 ` [PATCH 1/2] btrfs: make assert_rbio() to only check CONFIG_BTRFS_DEBUG Qu Wenruo
2024-09-16  9:05 ` [PATCH 2/2] btrfs: split out CONFIG_BTRFS_EXPERIMENTAL from CONFIG_BTRFS_DEBUG Qu Wenruo
2024-09-17 16:57   ` Filipe Manana
2024-09-16 10:58 ` [PATCH 0/2] " 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.1726477365.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