From: Bill Davidsen <davidsen@tmr.com>
To: ap23563m@gmx.com
Cc: linux-raid@vger.kernel.org
Subject: Re: About seting up Raid5 on a four disk box.
Date: Wed, 14 Oct 2009 17:08:58 -0400 [thread overview]
Message-ID: <4AD63DEA.8090906@tmr.com> (raw)
In-Reply-To: <hb4olr$6to$1@ger.gmane.org>
Antonio Perez wrote:
> Majed B. wrote:
>
>
>> Your applications can request as much files as they want regardless of
>> their location, but the mechanical heads move together, so they can be
>> at a single location at a point of time reading a single stream of a
>> file (or multiple files if they were next to each other on the
>> physical platter).
>>
>
> Yes that's completely correct, and it's the job of the "elevator" (*) on the
> "md" code to decide which sector, and in what order, such sectors will be
> serviced. If the "elevator" is aware of the underlying hardware, it will do
> the right thing if there are several md or just one.
>
>
The elevator is part of disk access, not md. It schedules head motion
for all users of the drive.
> *(I am not an expert on this, is just what I got from Robin)
>
>
--
Bill Davidsen <davidsen@tmr.com>
Unintended results are the well-earned reward for incompetence.
next prev parent reply other threads:[~2009-10-14 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 13:13 About seting up Raid5 on a four disk box Antonio Perez
2009-10-13 14:04 ` Majed B.
2009-10-13 14:52 ` Antonio Perez
2009-10-13 15:10 ` Majed B.
2009-10-14 6:23 ` Antonio Perez
2009-10-14 6:40 ` Majed B.
2009-10-14 12:53 ` Antonio Perez
2009-10-14 13:41 ` Majed B.
2009-10-14 14:53 ` Antonio Perez
2009-10-14 21:08 ` Bill Davidsen [this message]
2009-10-13 15:23 ` Robin Hill
2009-10-14 7:45 ` Antonio Perez
2009-10-14 8:56 ` Robin Hill
2009-10-14 12:55 ` Antonio Perez
2009-10-13 20:54 ` Bill Davidsen
2009-10-14 7:49 ` Antonio Perez
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=4AD63DEA.8090906@tmr.com \
--to=davidsen@tmr.com \
--cc=ap23563m@gmx.com \
--cc=linux-raid@vger.kernel.org \
/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.