public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] btrfs: scrub: finish the switch to scrub_stripe and cleanup the old code
Date: Wed, 29 Mar 2023 15:09:44 +0800	[thread overview]
Message-ID: <cover.1680073696.git.wqu@suse.com> (raw)

This series is based on my previous patchset "v7 btrfs: scrub: use a
more reader friendly code to implement scrub_simple_mirror()", the whole
series can be fetched from github:

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

After the mentioned patchset, only one path, scrub_raid56_parity(), is
still using the old facility.

[PATCH SPLIT]

This series would firstly migrate the only path to the new scrub_stripe
based solution.
The change should only affect RAID56, thus zoned mode should not be affected.

Then the remaining 5 patches to remove all the remaining code.
I have tried my best to split the cleanup, starting from RAID56 specific
code, to writeback, then approach the core scrub_bio facility.

If the split is not preferred, it should still be possible to fold all
the last 5 patches into one big cleanup.

[CODE SIZE REDUCTION]

The number of deletion should explain itself, and even with my previous
patchset included, it is still a big win:

 9 files changed, 1488 insertions(+), 2931 deletions(-)

Still a net reduce of almost 1500 lines.

Qu Wenruo (6):
  btrfs: scrub: use scrub_stripe to implement RAID56 P/Q scrub
  btrfs: scrub: remove scrub_parity structure
  btrfs: scrub: remove the old writeback infrastructure
  btrfs: scrub: remove the old scrub recheck code
  btrfs: scrub: remove scrub_block and scrub_sector structures
  btrfs: scrub: remove scrub_bio structure

 fs/btrfs/block-group.c |   11 -
 fs/btrfs/block-group.h |    8 -
 fs/btrfs/fs.h          |    1 -
 fs/btrfs/scrub.c       | 2740 ++++------------------------------------
 4 files changed, 212 insertions(+), 2548 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-03-29  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  7:09 Qu Wenruo [this message]
2023-03-29  7:09 ` [PATCH 1/6] btrfs: scrub: use scrub_stripe to implement RAID56 P/Q scrub Qu Wenruo
2023-03-29  7:09 ` [PATCH 2/6] btrfs: scrub: remove scrub_parity structure Qu Wenruo
2023-03-29  7:09 ` [PATCH 3/6] btrfs: scrub: remove the old writeback infrastructure Qu Wenruo
2023-03-29  7:09 ` [PATCH 4/6] btrfs: scrub: remove the old scrub recheck code Qu Wenruo
2023-03-29  7:09 ` [PATCH 5/6] btrfs: scrub: remove scrub_block and scrub_sector structures Qu Wenruo
2023-03-29  7:09 ` [PATCH 6/6] btrfs: scrub: remove scrub_bio structure 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.1680073696.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