All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 00/12] btrfs: scrub: use a more reader friendly code to implement scrub_simple_mirror()
Date: Tue, 21 Mar 2023 01:09:18 +0100	[thread overview]
Message-ID: <20230321000918.GI10580@twin.jikos.cz> (raw)
In-Reply-To: <cover.1679278088.git.wqu@suse.com>

On Mon, Mar 20, 2023 at 10:12:46AM +0800, Qu Wenruo wrote:
> [TODO]
> 
> - More testing on zoned devices
>   Now the patchset can already pass all scrub/replace groups with
>   regular devices.

I think I noticed some disparity in the old and new code for the zoned
devices. This should be found by testing so I'd add this series to
for-next and see.

> - More cleanup on RAID56 path
>   Now RAID56 still uses some old facility, resulting things like
>   scrub_sector and scrub_bio can not be fully cleaned up.

We can do that incrementally, as long as the raid56 scrub works the
cleanups can be done later, the series changes a lot of code already.

> Qu Wenruo (12):
>   btrfs: scrub: use dedicated super block verification function to scrub
>     one super block
>   btrfs: introduce a new helper to submit bio for scrub
>   btrfs: introduce a new helper to submit write bio for scrub
>   btrfs: scrub: introduce the structure for new BTRFS_STRIPE_LEN based
>     interface
>   btrfs: scrub: introduce a helper to find and fill the sector info for
>     a scrub_stripe
>   btrfs: scrub: introduce a helper to verify one metadata
>   btrfs: scrub: introduce a helper to verify one scrub_stripe
>   btrfs: scrub: introduce the main read repair worker for scrub_stripe
>   btrfs: scrub: introduce a writeback helper for scrub_stripe
>   btrfs: scrub: introduce error reporting functionality for scrub_stripe
>   btrfs: scrub: introduce the helper to queue a stripe for scrub
>   btrfs: scrub: switch scrub_simple_mirror() to scrub_stripe
>     infrastructure

The whole series follows the pattern to first introduce the individual
helpers that can be reviewed separately and then does the switch in one
patch. As the whole scrub IO path is reworked I don't think we can do
much better so clearly separating the old and new logic sounds OK.

One comment I have, the functional switch in the last patch should not
be mixed with deleting of the unused code. As the last patch activates
code from all the previous patches it would also show up in any
bisection as the cause so it would help to narrow the focus only on the
real changes.

There are some minor coding style issues I'll point out under the
patches. I'm assuming that the scrub structure won't change again soon
(the old code is from 3.x times) so let's use this opportunity to make
the style most up to date.

  parent reply	other threads:[~2023-03-21  0:15 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  2:12 [PATCH v3 00/12] btrfs: scrub: use a more reader friendly code to implement scrub_simple_mirror() Qu Wenruo
2023-03-20  2:12 ` [PATCH v3 01/12] btrfs: scrub: use dedicated super block verification function to scrub one super block Qu Wenruo
2023-03-21  5:22   ` Anand Jain
2023-03-21  7:25     ` Qu Wenruo
2023-03-21 22:12       ` David Sterba
2023-03-20  2:12 ` [PATCH v3 02/12] btrfs: introduce a new helper to submit bio for scrub Qu Wenruo
2023-03-21 12:02   ` Christoph Hellwig
2023-03-24  9:58     ` Qu Wenruo
2023-03-25  8:09       ` Christoph Hellwig
2023-03-25  8:21         ` Qu Wenruo
2023-03-25  8:31           ` Christoph Hellwig
2023-03-25  8:48             ` Qu Wenruo
2023-03-27  3:36               ` Christoph Hellwig
2023-03-20  2:12 ` [PATCH v3 03/12] btrfs: introduce a new helper to submit write " Qu Wenruo
2023-03-21  0:14   ` David Sterba
2023-03-21  0:54     ` Qu Wenruo
2023-03-21  1:27       ` David Sterba
2023-03-23  8:48     ` Qu Wenruo
2023-03-20  2:12 ` [PATCH v3 04/12] btrfs: scrub: introduce the structure for new BTRFS_STRIPE_LEN based interface Qu Wenruo
2023-03-21  0:22   ` David Sterba
2023-03-20  2:12 ` [PATCH v3 05/12] btrfs: scrub: introduce a helper to find and fill the sector info for a scrub_stripe Qu Wenruo
2023-03-20  2:12 ` [PATCH v3 06/12] btrfs: scrub: introduce a helper to verify one metadata Qu Wenruo
2023-03-21  0:31   ` David Sterba
2023-03-20  2:12 ` [PATCH v3 07/12] btrfs: scrub: introduce a helper to verify one scrub_stripe Qu Wenruo
2023-03-20  2:12 ` [PATCH v3 08/12] btrfs: scrub: introduce the main read repair worker for scrub_stripe Qu Wenruo
2023-03-20  2:12 ` [PATCH v3 09/12] btrfs: scrub: introduce a writeback helper " Qu Wenruo
2023-03-21  0:43   ` David Sterba
2023-03-20  2:12 ` [PATCH v3 10/12] btrfs: scrub: introduce error reporting functionality " Qu Wenruo
2023-03-20  2:12 ` [PATCH v3 11/12] btrfs: scrub: introduce the helper to queue a stripe for scrub Qu Wenruo
2023-03-20  2:12 ` [PATCH v3 12/12] btrfs: scrub: switch scrub_simple_mirror() to scrub_stripe infrastructure Qu Wenruo
2023-03-21  1:12   ` David Sterba
2023-03-21  0:09 ` David Sterba [this message]
2023-03-23  6:28   ` [PATCH v3 00/12] btrfs: scrub: use a more reader friendly code to implement scrub_simple_mirror() Qu Wenruo
2023-03-23 17:51     ` David Sterba
2023-03-24  0:42       ` Qu Wenruo
2023-03-27 23:28         ` 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=20230321000918.GI10580@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.