From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/7] btrfs-progs: cmds/tune: add set/clear features
Date: Tue, 5 Sep 2023 15:51:42 +0800 [thread overview]
Message-ID: <cover.1693900169.git.wqu@suse.com> (raw)
This is the first step to convert btrfstune functionality to "btrfs
tune" subcommand group.
For now only binary features, aka set and clear, is supported,
thus uuid and csum change is not yet implemented.
(Both need their own subcommand groups other than set/clear groups)
And even for set/clear, there is some changes to btrfstune:
- Merge seed feature into set/clear
To enable seeding, just go "btrfs tune set seed <device>".
- All supported features can be checked by "list-all" feature
Please note that, "btrfs tune set list-all" and
"btrfs tune clear list-all" will have different output.
The reason is some fundamental features like no-holes can not be
disabled.
Qu Wenruo (7):
btrfs-progs: export btrfs_feature structure
btrfs-progs: cmds: add "btrfs tune set" subcommand group
btrfs-progs: cmds/tune: add set support for free-space-tree feature
btrfs-progs: cmds/tune: add set support for block-group-tree feature
btrfs-progs: cmds/tune: add set support for seeding device
btrfs-progs: cmds/tune: add "btrfs tune clear" subcommand
btrfs-progs: tests/cli: add a test case for "btrfs tune" subcommand
Documentation/btrfs-tune.rst | 47 +++
Documentation/btrfs.rst | 5 +
Documentation/conf.py | 1 +
Documentation/man-index.rst | 1 +
Makefile | 4 +-
btrfs.c | 1 +
cmds/commands.h | 1 +
cmds/tune.c | 448 +++++++++++++++++++++++++
common/fsfeatures.c | 53 ---
common/fsfeatures.h | 50 +++
tests/cli-tests/018-btrfs-tune/test.sh | 40 +++
11 files changed, 596 insertions(+), 55 deletions(-)
create mode 100644 Documentation/btrfs-tune.rst
create mode 100644 cmds/tune.c
create mode 100755 tests/cli-tests/018-btrfs-tune/test.sh
--
2.42.0
next reply other threads:[~2023-09-05 16:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 7:51 Qu Wenruo [this message]
2023-09-05 7:51 ` [PATCH 1/7] btrfs-progs: export btrfs_feature structure Qu Wenruo
2023-09-21 0:32 ` Anand Jain
2023-09-21 21:35 ` Qu Wenruo
2023-09-05 7:51 ` [PATCH 2/7] btrfs-progs: cmds: add "btrfs tune set" subcommand group Qu Wenruo
2023-09-21 0:53 ` Anand Jain
2023-09-21 2:13 ` Qu Wenruo
2023-10-13 17:47 ` David Sterba
2023-10-30 8:26 ` Anand Jain
2023-09-05 7:51 ` [PATCH 3/7] btrfs-progs: cmds/tune: add set support for free-space-tree feature Qu Wenruo
2023-09-05 7:51 ` [PATCH 4/7] btrfs-progs: cmds/tune: add set support for block-group-tree feature Qu Wenruo
2023-09-05 7:51 ` [PATCH 5/7] btrfs-progs: cmds/tune: add set support for seeding device Qu Wenruo
2023-09-05 7:51 ` [PATCH 6/7] btrfs-progs: cmds/tune: add "btrfs tune clear" subcommand Qu Wenruo
2023-09-05 7:51 ` [PATCH 7/7] btrfs-progs: tests/cli: add a test case for "btrfs tune" subcommand Qu Wenruo
2023-09-20 23:03 ` [PATCH 0/7] btrfs-progs: cmds/tune: add set/clear features Qu Wenruo
2023-09-21 22:33 ` waxhead
2023-09-21 22:53 ` Qu Wenruo
2023-10-13 17:55 ` David Sterba
2023-10-13 18:50 ` David Sterba
2023-10-13 20:53 ` 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.1693900169.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;
as well as URLs for NNTP newsgroup(s).