From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 3/4] btrfs: submit read time repair only for each corrupted sector
Date: Tue, 11 May 2021 13:35:44 +0200 [thread overview]
Message-ID: <20210511113544.GG7604@twin.jikos.cz> (raw)
In-Reply-To: <751b7396-d0fd-d3b2-f14d-e730e6b08222@gmx.com>
On Tue, May 11, 2021 at 09:42:30AM +0800, Qu Wenruo wrote:
>
>
> On 2021/5/11 上午4:32, David Sterba wrote:
> > On Mon, May 03, 2021 at 10:08:55AM +0800, Qu Wenruo wrote:
> >> Currently btrfs_submit_read_repair() has some extra check on whether the
> >> failed bio needs extra validation for repair.
> >>
> >> But we can avoid all these extra mechanism if we submit the repair for
> >> each sector.
> >>
> >> By this, each read repair can be easily handled without the need to
> >> verify which sector is corrupted.
> >>
> >> This will also benefit subpage, as one subpage bvec can contain several
> >> sectors, making the extra verification more complex.
> >>
> >> So this patch will:
> >> - Introduce repair_one_sector()
> >> The main code submitting repair, which is more or less the same as old
> >> btrfs_submit_read_repair().
> >> But this time, it only repair one sector.
> >>
> >> - Make btrfs_submit_read_repair() to handle sectors differently
> >> For sectors without csum error, just release them like what we did
> >> in end_bio_extent_readpage().
> >> Although in this context we don't have process_extent structure, thus
> >> we have to do extent tree operations sector by sector.
> >> This is slower, but since it's only in csum mismatch path, it should
> >> be fine.
> >>
> >> For sectors with csum error, we submit repair for each sector.
> >>
> >> This patch will focus on the change on the repair path, the extra
> >> validation code is still kept as is, and will be cleaned up later.
> >
> > This leaves btrfs_io_needs_validation unused and compiler warns about
> > that but it gets removed in the next patch so that's ok.
> >
> > I did some minor style fixups
> >
> > --- a/fs/btrfs/extent_io.c
> > +++ b/fs/btrfs/extent_io.c
> > @@ -2706,7 +2706,7 @@ static void end_page_read(struct page *page, bool uptodate, u64 start, u32 len)
> > struct btrfs_fs_info *fs_info = btrfs_sb(page->mapping->host->i_sb);
> >
> > ASSERT(page_offset(page) <= start &&
> > - start + len <= page_offset(page) + PAGE_SIZE);
> > + start + len <= page_offset(page) + PAGE_SIZE);
> >
> > if (uptodate) {
> > btrfs_page_set_uptodate(fs_info, page, start, len);
> > @@ -2734,7 +2734,7 @@ blk_status_t btrfs_submit_read_repair(struct inode *inode,
> > {
> > struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
> > const u32 sectorsize = fs_info->sectorsize;
> > - int nr_bits = (end + 1 - start) / sectorsize;
> > + const int nr_bits = (end + 1 - start) / fs_info->sectorsize_bits;
>
> It should be >> fs_info->sectorsize_bits;
>
> Anyway, I'll submit a proper updated version, with your update and
> proper test.
My bad, thanks for catching it.
next prev parent reply other threads:[~2021-05-11 11:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 2:08 [PATCH v3 0/4] btrfs: make read time repair to be only submitted for each corrupted sector Qu Wenruo
2021-05-03 2:08 ` [PATCH v3 1/4] btrfs: remove the dead branch in btrfs_io_needs_validation() Qu Wenruo
2021-05-03 17:05 ` David Sterba
2021-05-03 23:39 ` Qu Wenruo
2021-05-10 20:14 ` David Sterba
2021-05-10 23:56 ` Qu Wenruo
2021-05-11 11:27 ` David Sterba
2021-05-03 2:08 ` [PATCH v3 2/4] btrfs: make btrfs_verify_data_csum() to return a bitmap Qu Wenruo
2021-05-03 2:08 ` [PATCH v3 3/4] btrfs: submit read time repair only for each corrupted sector Qu Wenruo
2021-05-10 20:32 ` David Sterba
2021-05-11 1:42 ` Qu Wenruo
2021-05-11 11:35 ` David Sterba [this message]
2021-05-03 2:08 ` [PATCH v3 4/4] btrfs: remove io_failure_record::in_validation Qu Wenruo
2021-05-10 20:41 ` [PATCH v3 0/4] btrfs: make read time repair to be only submitted for each corrupted sector David Sterba
2021-05-11 1:07 ` Qu Wenruo
2021-05-11 11:59 ` 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=20210511113544.GG7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox