linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: scrub: cleanup scrub_raid56_parity() using find_first_extent_item() helper
Date: Fri,  7 Jan 2022 15:09:49 +0800	[thread overview]
Message-ID: <20220107070951.48246-1-wqu@suse.com> (raw)

This patchset is depedent on previous patchset titled "btrfs: refactor
scrub entrances for each profile", and can be fetched from github:

https://github.com/adam900710/linux/tree/refactor_scrub

This patchset is doing the remaining cleanup for extent item iteration
of scrub_raid56_parity().

As that function is mostly a variant of scrub_simple_mirror() with
different target operations.

This patchset will refactor a double while loops into a single while
loop with a helper, then cleanup the open-coded extent item lookup code.

With this patchset, all extent item iteration code will share the new
find_first_extent_item() based solution.

Qu Wenruo (2):
  btrfs: refactor scrub_raid56_parity()
  btrfs: use find_first_extent_item() to replace the open-coded extent
    item search

 fs/btrfs/scrub.c | 299 +++++++++++++++++++----------------------------
 1 file changed, 118 insertions(+), 181 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-01-07  7:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  7:09 Qu Wenruo [this message]
2022-01-07  7:09 ` [PATCH 1/2] btrfs: refactor scrub_raid56_parity() Qu Wenruo
2022-01-07  8:20   ` Damien Le Moal
2022-01-07  9:52     ` Qu Wenruo
2022-01-07  7:09 ` [PATCH 2/2] btrfs: use find_first_extent_item() to replace the open-coded extent item search 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=20220107070951.48246-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).