From: Jens Axboe <axboe@suse.de>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
Neil Brown <neilb@suse.de>
Subject: Re: raid and elevator
Date: Mon, 27 Mar 2006 14:27:47 +0200 [thread overview]
Message-ID: <20060327122747.GK8186@suse.de> (raw)
In-Reply-To: <5d96567b0603261329o39a5e777w5bc39ad5251b4ecb@mail.gmail.com>
On Sun, Mar 26 2006, Raz Ben-Jehuda(caro) wrote:
> It is my belief that the linux elevators are not optimized for
> raid throughout.
>
> Basically when IO initiator generates IO over a single disk he can control
> the amount of IOs and this way control IOs latencies.
>
> This is not the case in raided volumes.
>
> Example:
>
> An IO initiator intiates bulks of asynchronous IOs over a raided
> volume. since the user does not know the target destination of each IO
> he
> might cause imbalance over the disks. one disk may become overflooded
> with IOs while the other is may starve. So eventually we are ending with
> a non balaned raided volume in terms of bad latencies.
>
> I am trying to deal with this problem by fixing the deadline elevator code
> to batch IOs , meaning , when n IOs are reaching the disk, each m deadlined
> IOs are sorted and then dispatced.
You do realize that the io scheduler resides _below_ the raid
personality? So if you want to balance what goes to what io scheduler
(and thus, disk), you'd want to mess with the raid personality.
--
Jens Axboe
next prev parent reply other threads:[~2006-03-27 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:29 raid and elevator Raz Ben-Jehuda(caro)
2006-03-27 12:27 ` Jens Axboe [this message]
[not found] ` <5d96567b0603270436x69eba93cx4b55b942c422afe0@mail.gmail.com>
[not found] ` <20060327123951.GL8186@suse.de>
2006-03-27 12:42 ` Raz Ben-Jehuda(caro)
2006-03-27 12:44 ` Jens Axboe
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=20060327122747.GK8186@suse.de \
--to=axboe@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=raziebe@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).