linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Neil Brown <neilb@suse.de>
Cc: Alex Tomas <alex@clusterfs.com>, linux-raid@vger.kernel.org
Subject: Re: linear writes to raid5
Date: Tue, 18 Apr 2006 18:28:56 +0400	[thread overview]
Message-ID: <4444F7A8.7050304@tls.msk.ru> (raw)
In-Reply-To: <17474.53696.831154.37427@cse.unsw.edu.au>

Neil Brown wrote:
[]
> raid5 shouldn't need to merge small requests into large requests.
> That is what the 'elevator' or io_scheduler algorithms are for.  There
> already merge multiple bio's into larger 'requests'.  If they aren't
> doing that, then something needs to be fixed.
> 
> It is certainly possible that raid5 is doing something wrong that
> makes merging harder - maybe sending bios in the wrong order, or
> sending them with unfortunate timing.  And if that is the case it
> certainly makes sense to fix it.  
> But I really don't see that raid5 should be merging requests together
> - that is for a lower-level to do.

Hmm.  So where's the elevator level - before raid level (between e.g.
a filesystem and md), or after it (between md and physical devices) ?

I mean, mergeing bios into larger requests makes alot of sense between
a filesystem and md levels, but it makes alot less sense to do that
between md and physical (fsvo "physical" anyway) disks.

Thanks.

/mjt


  reply	other threads:[~2006-04-18 14:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08  0:17 linear writes to raid5 Alex Tomas
2006-04-09 20:24 ` Mark Hahn
2006-04-11 20:55   ` Alex Tomas
2006-04-10  0:50 ` Neil Brown
2006-04-11 21:05   ` Alex Tomas
2006-04-12  0:15     ` Neil Brown
2006-04-12 15:50       ` Alex Tomas
2006-04-12 16:01         ` Alex Tomas
2006-04-16 23:22         ` Neil Brown
2006-04-18 14:28           ` Michael Tokarev [this message]
2006-04-19 19:43             ` Alex Tomas
2006-04-19 23:44             ` Neil Brown
2006-04-20  8:22               ` Michael Tokarev
2006-04-27  0:18                 ` Neil Brown
2006-04-19 19:40           ` Alex Tomas
2006-04-19 23:54             ` Neil Brown

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=4444F7A8.7050304@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=alex@clusterfs.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).