From: Paul Clements <paul.clements@steeleye.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [BUG] raid1: barrier retry does not work correctly with write-behind
Date: Thu, 03 Aug 2006 23:09:14 -0400 [thread overview]
Message-ID: <44D2BA5A.3020809@steeleye.com> (raw)
In-Reply-To: <17618.42801.411938.763485@cse.unsw.edu.au>
Neil Brown wrote:
> sector, bdev, size are all remembered in r1_bio.
> That leaves bi_idx and an array od len/offset pairs that we need
> to preserve.
>
> So I guess the first step is to change alloc_behind_pages to
> return a new 'struct bio_vec' array rather than just a list of pages,
> and we should keep that array attached to the raid1_bio.
I think bio_clone gives us that already. I may have missed something but
I think we have everything we need:
When a bio comes into raid1's make_request we bio_clone for each drive
and attach those to r1_bio->bios. We also have behind_pages, which
contains the pages. I think maybe instead of cloning r1_bio->master_bio,
we can just clone r1_bio->bios[i]. Does that make sense?
Let me try that.
--
Paul
next prev parent reply other threads:[~2006-08-04 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 15:44 [BUG] raid1: barrier retry does not work correctly with write-behind Paul Clements
2006-08-04 1:47 ` Neil Brown
2006-08-04 3:09 ` Paul Clements [this message]
2006-08-04 3:35 ` Paul Clements
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=44D2BA5A.3020809@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).