All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: hide block group tree behind experimental feature
Date: Thu, 22 Sep 2022 06:20:25 +0800	[thread overview]
Message-ID: <ecd14905-6ff1-3d26-7354-93631684fa0c@gmx.com> (raw)
In-Reply-To: <20220921140611.GG32411@twin.jikos.cz>



On 2022/9/21 22:06, David Sterba wrote:
> On Mon, Sep 12, 2022 at 11:12:01AM +0800, Qu Wenruo wrote:
>> The block group tree doesn't yet have full bi-directional conversion
>> support from btrfstune, and it seems we may want one or two release
>> cycles to rule out some extra bugs before really releasing the progs
>> support.
>>
>> This patch will hide the block group tree feature behind experimental
>> flag for the following tools:
>>
>> - btrfstune
>>    "-b" option to convert to bg tree.
>>
>> - mkfs.btrfs
>>    hide "block-group-tree" feature from both -O (the new default position
>>    for all features) and -R (the old, soon to be deprecated one).
>
> The block group tree is going to 6.1, so the progs support will be
> experimental in 6.0 and enabled no later than 6.1. It might be enabled
> earlier so we can use the normal build in testing.

Personally speaking, I'd hope bg tree would be hidden behind
experimental until the bi-directional convert is implemented.

(AKA, I should finish the remaining part of the btrfstune for bg tree)

Thanks,
Qu

  reply	other threads:[~2022-09-21 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12  3:12 [PATCH] btrfs-progs: hide block group tree behind experimental feature Qu Wenruo
2022-09-21 14:06 ` David Sterba
2022-09-21 22:20   ` Qu Wenruo [this message]
2022-09-22 13:46     ` David Sterba

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=ecd14905-6ff1-3d26-7354-93631684fa0c@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=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 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.