From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/7] btrfs-progs: Support for BG_TREE feature
Date: Thu, 10 Oct 2019 14:41:49 +0800 [thread overview]
Message-ID: <20191010064156.31782-1-wqu@suse.com> (raw)
This patchset can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/bg_tree
Which is based on v5.2.2 tag.
This patchset provides the needed user space infrastructure for BG_TREE
feature.
Since it's an new incompatible feature, unlike SKINNY_METADATA, btrfs-progs
is needed to convert existing fs (unmounted) to new format.
Now btrfstune can convert regular extent tree fs to bg tree fs to
improve mount time.
For the performance improvement, please check the kernel patchset cover
letter or the last patch.
(SPOILER ALERT: It's super fast)
Changelog:
v2:
- Rebase to v5.2.2 tag
- Add btrfstune ability to convert existing fs to BG_TREE feature
v3:
- Fix a bug that temp chunks are not cleaned up properly
This is caused by wrong timing btrfs_convert_to_bg_tree() is called.
It should be called after temp chunks cleaned up.
- Fix a bug that an extent buffer get leaked
This is caused by newly created bg tree not added to dirty list.
Qu Wenruo (7):
btrfs-progs: Refactor excluded extent functions to use fs_info
btrfs-progs: Refactor btrfs_read_block_groups()
btrfs-progs: Enable read-write ability for 'bg_tree' feature
btrfs-progs: mkfs: Introduce -O bg-tree
btrfs-progs: dump-tree/dump-super: Introduce support for bg tree
btrfs-progs: check: Introduce support for bg-tree feature
btrfs-progs: btrfstune: Allow to enable bg-tree feature offline
Documentation/btrfstune.asciidoc | 6 +
btrfstune.c | 44 +++-
check/main.c | 7 +-
check/mode-lowmem.c | 9 +-
cmds/inspect-dump-super.c | 3 +-
cmds/inspect-dump-tree.c | 5 +
common/fsfeatures.c | 6 +
ctree.h | 18 +-
disk-io.c | 29 ++-
extent-tree.c | 365 +++++++++++++++++++++++--------
mkfs/common.c | 6 +-
mkfs/main.c | 25 +++
print-tree.c | 3 +
transaction.c | 1 +
14 files changed, 419 insertions(+), 108 deletions(-)
--
2.23.0
next reply other threads:[~2019-10-10 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 6:41 Qu Wenruo [this message]
2019-10-10 6:41 ` [PATCH v3 1/7] btrfs-progs: Refactor excluded extent functions to use fs_info Qu Wenruo
2019-10-10 6:41 ` [PATCH v3 2/7] btrfs-progs: Refactor btrfs_read_block_groups() Qu Wenruo
2019-10-10 6:41 ` [PATCH v3 3/7] btrfs-progs: Enable read-write ability for 'bg_tree' feature Qu Wenruo
2019-10-10 6:41 ` [PATCH v3 4/7] btrfs-progs: mkfs: Introduce -O bg-tree Qu Wenruo
2019-10-10 6:41 ` [PATCH v3 5/7] btrfs-progs: dump-tree/dump-super: Introduce support for bg tree Qu Wenruo
2019-10-10 6:41 ` [PATCH v3 6/7] btrfs-progs: check: Introduce support for bg-tree feature Qu Wenruo
2019-10-10 6:41 ` [PATCH v3 7/7] btrfs-progs: btrfstune: Allow to enable bg-tree feature offline Qu Wenruo
2019-10-21 15:26 ` [PATCH v3 0/7] btrfs-progs: Support for BG_TREE feature 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=20191010064156.31782-1-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).