From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: relocation: build_backref_cache() refactor part 2
Date: Mon, 24 Feb 2020 14:01:57 +0800 [thread overview]
Message-ID: <20200224060200.31323-1-wqu@suse.com> (raw)
This patchset can be fetched from:
https://github.com/adam900710/linux/tree/backref_cache_new
Since it is based on previous btrfs_backref_iter facility, it's
recommended to fetch from above repo.
This patchset mostly refactors the backref handling code out of the bit
loop in build_backref_cache().
Now build_backref_tree() can be easily divided into 4 small parts:
- Basic structure allocation
- Breadth-first search for backrefs
- Handling edges of upper nodes
- Removing useless nodes
Qu Wenruo (3):
btrfs: relocation: Use wrapper to replace open-coded edge linking
btrfs: relocation: Specify essential members for alloc_backref_node()
btrfs: relocation: Remove the open-coded goto loop for breadth-first
search
fs/btrfs/relocation.c | 241 ++++++++++++++++++++++++------------------
1 file changed, 138 insertions(+), 103 deletions(-)
--
2.25.1
next reply other threads:[~2020-02-24 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 6:01 Qu Wenruo [this message]
2020-02-24 6:01 ` [PATCH 1/3] btrfs: relocation: Use wrapper to replace open-coded edge linking Qu Wenruo
2020-02-27 19:39 ` Josef Bacik
2020-02-24 6:01 ` [PATCH 2/3] btrfs: relocation: Specify essential members for alloc_backref_node() Qu Wenruo
2020-02-27 19:40 ` Josef Bacik
2020-02-24 6:02 ` [PATCH 3/3] btrfs: relocation: Remove the open-coded goto loop for breadth-first search Qu Wenruo
2020-02-27 19:51 ` Josef Bacik
2020-02-28 0:08 ` Qu Wenruo
2020-02-28 0:15 ` 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=20200224060200.31323-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