From: Yuehai Xu <yuehaixu@gmail.com>
To: linux-raid@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yhxu@wayne.edu, czoccolo@gmail.com,
neilb@suse.de, jens.axboe@oracle.com
Subject: Questions about RAID and I/O scheduler
Date: Wed, 31 Mar 2010 16:24:09 -0400 [thread overview]
Message-ID: <m2v100eff551003311324tdc2e567atd2a48e35520e8601@mail.gmail.com> (raw)
Hi,
I noticed that some one said NOOP is usually the default I/O scheduler
for hardware RAID. Why not CFQ? Suppose there are just several
sequential read processes, as I know CFQ will keep all the disk heads
of hard raid to serve a process for a while(a time slice), in that
case, CFQ should be the best of all I/O schedulers. Am I right?
Generally, hard raid should have its own I/O scheduler in their
firmware, in that case, the I/O scheduler of OS should do nothing
except dispatch the requests as soon as possible, it is the hard raid
itself to decide how to schedule these requests. From this point of
view, NOOP should be the default one. I am really confused here.
The next question is about the maximal number of disks in disk array,
the fault tolerance should be one limitation because the more the
number of disks, the higher chance of failure. However, may throughput
also be one limitation? Do you know anyone use disk array which
contains large number of disks to handle small requests? Such as 256
disks to handle 4K requests?
Thanks!
Yuehai
next reply other threads:[~2010-03-31 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 20:24 Yuehai Xu [this message]
2010-04-02 8:02 ` Questions about RAID and I/O scheduler Corrado Zoccolo
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=m2v100eff551003311324tdc2e567atd2a48e35520e8601@mail.gmail.com \
--to=yuehaixu@gmail.com \
--cc=czoccolo@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=yhxu@wayne.edu \
/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).