All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: Neil Brown <neilb@suse.de>
Cc: Ingo Molnar <mingo@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: [patch] latency problem in md driver
Date: Tue, 26 Dec 2006 14:09:37 +0100	[thread overview]
Message-ID: <20061226130937.GA19869@barkeeper1.linbit> (raw)
In-Reply-To: <17804.17074.430522.825100@cse.unsw.edu.au>

/ 2006-12-23 07:40:18 +1100
\ Neil Brown:
> On Friday December 22, Lars.Ellenberg@linbit.com wrote:
> > 
> > md raidX make_request functions strip off the BIO_RW_SYNC flag,
> > this introducing additional latency.
> > 
> > below is a suggested patch for the raid1.c .
> > other suggested solutions would be to let the bio_clone do its work,
> > and not reassign thereby stripping off all flags.
> > at most strip off known unwanted flags (the BARRIER flag).
> > 
> > similar pattern in the other raid versions.
> 
> Thanks.  I think your patch is appropriate.
> I don't like the idea of passing down any flags by default.  If a flag
> makes failure more likely (like BIO_RW_AHEAD or BIO_RW_FAILFAST) then
> I *don't* want it passed down without making a conscious decision that
> it is a good idea.
> 
> So yes, _SYNC should be passed down in raid1/raid10.  More interesting
> stuff would be needed in raid456.
> _FAILFAST should probably never be passed down (well, maybe in
> multipath, but who uses md/multipath??)
> _META ... what is that ?? I'm not passing it down until I know!!
> 
> I'll look into this after the holidays.  Meanwhile if you want to be
> certain that this is in 2.6.20,
>   - Fix the retry-read case as well (where ->bi_rw is assigned about
>     10 lines from the end of raid1d()

I don't think thats necessary,
since an explicit unplug is in place there.
but ok.

>   - Create a 'perfect patch',
>   - add Acked-by: NeilBrown <neilb@suse.de>
>   - and post it to akpm@osdl.org (and appropriate lists).

-- 
: Lars Ellenberg                            Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :

      reply	other threads:[~2006-12-26 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22 14:32 [patch] latency problem in md driver Lars Ellenberg
2006-12-22 15:19 ` Jeff Garzik
2006-12-22 15:37   ` Ric Wheeler
2006-12-22 15:40   ` Lars Ellenberg
2006-12-22 17:33     ` Lars Ellenberg
2006-12-22 20:40 ` Neil Brown
2006-12-26 13:09   ` Lars Ellenberg [this message]

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=20061226130937.GA19869@barkeeper1.linbit \
    --to=lars.ellenberg@linbit.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 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.