From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH 0/2] Preparation for later btrfs_alloc_chunk() rework, Part 2
Date: Fri, 5 Jan 2018 16:12:10 +0800 [thread overview]
Message-ID: <20180105081212.27175-1-wqu@suse.com> (raw)
This patchset, along with its prerequisite (patchset named:
"[PATCH 0/5] Cleanups for later btrfs_alloc_chunk() rework") can be
fetched from github:
https://github.com/adam900710/btrfs-progs/tree/chunk_alloc_enospc
This patchset can still be treated as cleanup, but brings a much larger
structure modification of btrfs_alloc_chunk().
The first patch will merge the original btrfs_alloc_data_chunk() with
more generic btrfs_alloc_chunk().
And 2nd patch integrate btrfs_make_block_group() into
btrfs_alloc_chunk(), provides the critical basis for later rework.
(Later rework needs to update space info before any tree modification,
so btrfs_make_block_group must be integrated)
Considering the importance of btrfs_alloc_chunk() in btrfs-progs, these
2 patches are separated out for a longer review window before larger
rework.
Qu Wenruo (2):
btrfs-progs: Merge btrfs_alloc_data_chunk into btrfs_alloc_chunk
btrfs-progs: Make btrfs_alloc_chunk to handle block group creation
convert/main.c | 10 +--
extent-tree.c | 12 +---
mkfs/main.c | 42 ++---------
volumes.c | 222 +++++++++++++++++++++++----------------------------------
volumes.h | 5 +-
5 files changed, 102 insertions(+), 189 deletions(-)
--
2.15.1
next reply other threads:[~2018-01-05 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 8:12 Qu Wenruo [this message]
2018-01-05 8:12 ` [PATCH 1/2] btrfs-progs: Merge btrfs_alloc_data_chunk into btrfs_alloc_chunk Qu Wenruo
2018-01-05 9:36 ` Su Yue
2018-01-05 9:39 ` Su Yue
2018-01-05 9:44 ` Qu Wenruo
2018-01-08 8:25 ` [PATCH v2 " Qu Wenruo
2018-01-09 1:55 ` Su Yue
2018-01-05 8:12 ` [PATCH 2/2] btrfs-progs: Make btrfs_alloc_chunk to handle block group creation Qu Wenruo
2018-01-05 10:02 ` Su Yue
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=20180105081212.27175-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=dsterba@suse.cz \
--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).