From: Corey McGuire <coreyfro@coreyfro.com>
To: linux-raid@vger.kernel.org
Subject: Read-Balancing
Date: Sat, 31 Jan 2004 17:47:23 -0800 [thread overview]
Message-ID: <200401311747.23263.coreyfro@coreyfro.com> (raw)
Hey folks,
Quick question.
I have been reading up on read-balancing, and I understand that 2.6 has been tuned to have the drive head closest to the data perform the read to reduce seak times. This is neat, but can it prevent two disks from working together to read the same, nonfragmented file? Did read-balancing ever allow the ability for mirrored drives to work together on a sequential read? Seams that in a large read, each drive in a mirror could pick up a piece to read, and then reassembled the sequential read in RAM.
Also, does this prevent balancing multiple separate reads in the same file, or will the idle disk seak and read while the drive closer to the action is busy? Assuming, of course, the data isn't in cache.
Just therory stuff, really, but a curiosity none the less.
next reply other threads:[~2004-02-01 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 1:47 Corey McGuire [this message]
2004-02-02 4:56 ` Read-Balancing 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=200401311747.23263.coreyfro@coreyfro.com \
--to=coreyfro@coreyfro.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 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).