Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@keldix.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Read algorithm-raid1/raid10
Date: Tue, 18 Jan 2011 16:01:49 +0100	[thread overview]
Message-ID: <20110118150149.GB602@www2.open-std.org> (raw)
In-Reply-To: <AANLkTi=ULecH9g9Mt+axPY_KsyvZU=KdawphxpJ2kDGi@mail.gmail.com>

On Tue, Jan 18, 2011 at 12:00:49PM -0200, Roberto Spadim wrote:
> like this patch (a long time ago)
> http://www.spinics.net/lists/raid/msg30003.html
> 
> 
> 2011/1/18 Roberto Spadim <roberto@spadim.com.br>:
> > hi guys, could we implement a load_balance read algorithm for SSD?
> > nearest head isn't as fast as round robin for ssd.
> > i'm talking about raid1 (raid10 too)
> > what's my problem?
> > as i can see, raid0 is faster than raid1
> > for example:
> > two disks raid0 is faster than
> > two disks raid1.
> >
> > why?
> > nearest head
> > instead of a balanced read algorithm (like raid0) the nearest head
> > make raid1 use only one disk for searchs where we could use two disks
> > (like raid0)
> >
> > could we implement a round robin for ssd? and make raid1 as fast as
> > raid0 for ssd?
> > i didn't tested the raid10 algorithm yet.
> > thanks a lot.

This should only be in use for SSDs. For disks it would be a waste of IO
bandwidth. How do we detect whether it is a SSSD.
Another way to accomplish an improvement os to use the offset layout of
raid10.

best regards
Keld

  reply	other threads:[~2011-01-18 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 13:51 Read algorithm-raid1/raid10 Roberto Spadim
2011-01-18 14:00 ` Roberto Spadim
2011-01-18 15:01   ` Keld Jørn Simonsen [this message]
2011-01-18 15:51     ` Mathias Burén
2011-01-18 16:15       ` Roberto Spadim
2011-01-18 17:26         ` Roberto Spadim

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=20110118150149.GB602@www2.open-std.org \
    --to=keld@keldix.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=roberto@spadim.com.br \
    /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