All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
	linux-raid@vger.kernel.org
Subject: Re: RAID HDDs spin up sequence
Date: Tue, 01 Feb 2011 13:10:06 +0000	[thread overview]
Message-ID: <4D48062E.9040405@anonymous.org.uk> (raw)
In-Reply-To: <4D4765B2.7090002@cfl.rr.com>

On 01/02/2011 01:45, Phillip Susi wrote:
> On 01/31/2011 06:07 PM, Piergiorgio Sartor wrote:
>> That's interesting information. I suspected something
>> like async access could have happened.
>> Is this confirmed? Are the requests from md to the
>> device layer asynchronous?
>
> Yes, it sends down requests to all drives simultaneously to achieve
> maximum performance. This is the main purpose of raid-5.
>
>> How about libata? Does this serialize wake ups?
>
> It doesn't. It will wake them all up at once.
>
> If you want to force serial wakeup, you would need to do some hacking in
> libata or the scsi layer to only allow one wakeup request at once. Of
> course, with a 6 disk raid where each disk takes 6 seconds to spin up,
> you will be waiting 36 seconds to get your data. Not exactly desirable.

That'd be an excessive amount of time to wait. A quarter of a second is 
more than enough, a tenth of a second would probably be enough. It's 
just the motor inrush current you're trying to avoid having simultaneously.

So waiting another second for your array to wake up would mean you could 
use a sensibly-sized PSU operating in its 80%+ efficiency range, rather 
than a huge PSU operating inefficiently.

Cheers,

John.


  parent reply	other threads:[~2011-02-01 13:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 20:18 RAID HDDs spin up sequence Piergiorgio Sartor
2011-01-31 21:09 ` Roberto Spadim
2011-01-31 21:10   ` Roberto Spadim
2011-01-31 21:11   ` Mathias Burén
2011-01-31 21:25     ` Roberto Spadim
2011-01-31 21:29       ` Mathias Burén
2011-01-31 21:35         ` Roberto Spadim
2011-01-31 22:23   ` Piergiorgio Sartor
2011-01-31 22:42     ` Roberto Spadim
2011-01-31 22:42       ` Roberto Spadim
2011-01-31 23:07       ` Piergiorgio Sartor
2011-01-31 23:12         ` Roberto Spadim
2011-02-01  1:45         ` Phillip Susi
2011-02-01 12:39           ` Roman Mamedov
2011-02-01 13:10           ` John Robinson [this message]
2011-02-01 21:37             ` Stan Hoeppner
2011-02-01 22:46               ` Roberto Spadim
2011-02-01 13:55     ` brian.foster
2011-02-01 14:37       ` Roberto Spadim
2011-02-01 14:44         ` Roberto Spadim
2011-02-01 15:01           ` John Robinson
2011-02-01 15:46             ` 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=4D48062E.9040405@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=piergiorgio.sartor@nexgo.de \
    --cc=psusi@cfl.rr.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 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.