From: Paul Clements <paul.clements@steeleye.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Lars Roland <lroland@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux RAID M/L <linux-raid@vger.kernel.org>
Subject: Re: Poor Software RAID-0 performance with 2.6.14.2
Date: Tue, 22 Nov 2005 13:23:16 -0500 [thread overview]
Message-ID: <43836214.4010200@steeleye.com> (raw)
In-Reply-To: <438354B4.10604@tmr.com>
Bill Davidsen wrote:
> One of the advantages of mirroring is that if there is heavy read load
> when one drive is busy there is another copy of the data on the other
> drive(s). But doing 1MB reads on the mirrored device did not show that
> the kernel took advantage of this in any way. In fact, it looks as if
> all the reads are going to the first device, even with multiple
> processes running. Does the md code now set "write-mostly" by default
> and only go to the redundant drives if the first fails?
No, it doesn't use write-mostly by default. The way raid1 read balancing
works (in recent kernels) is this:
- sequential reads continue to go to the first disk
- for non-sequential reads, the code tries to pick the disk whose head
is "closest" to the sector that needs to be read
So even if the reads aren't exactly sequential, you probably still end
up reading from the first disk most of the time. I imagine with a more
random read pattern you'd see the second disk getting used.
--
Paul
next prev parent reply other threads:[~2005-11-22 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ad99e050511211231o97d5d7fw59b44527dc25dcea@mail.gmail.com>
2005-11-22 17:26 ` Poor Software RAID-0 performance with 2.6.14.2 Bill Davidsen
2005-11-22 18:23 ` Paul Clements [this message]
2005-11-22 21:39 ` Bill Davidsen
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=43836214.4010200@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lroland@gmail.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 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).