From: Arjan van de Ven <arjan@infradead.org>
To: "Phetteplace, Thad (GE Healthcare,
consultant)" <Thad.Phetteplace@ge.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bandwidth Allocations under CFQ I/O Scheduler
Date: Tue, 17 Oct 2006 03:24:29 +0200 [thread overview]
Message-ID: <1161048269.3245.26.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <CAEAF2308EEED149B26C2C164DFB20F4E7EAFE@ALPMLVEM06.e2k.ad.ge.com>
On Mon, 2006-10-16 at 16:46 -0400, Phetteplace, Thad (GE Healthcare,
consultant) wrote:
> The I/O priority levels available under the CFQ scheduler are
> nice (no pun in intended), but I remember some talk back when
> they first went in that future versions might include bandwidth
> allocations in addition to the 'niceness' style. Is anyone out
> there working on that? If not, I'm willing to hack up a proof
> of concept... I just wan't to make sure I'm not reinventing
> the wheel.
Hi,
it's a nice idea in theory. However... since IO bandwidth for seeks is
about 1% to 3% of that of sequential IO (on disks at least), which
bandwidth do you want to allocate? "worst case" you need to use the
all-seeks bandwidth, but that's so far away from "best case" that it may
well not be relevant in practice. Yet there are real world cases where
for a period of time you approach worst case behavior ;(
Greetings,
Arjan van de Ven
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-10-17 1:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 20:46 Phetteplace, Thad (GE Healthcare, consultant)
2006-10-17 1:24 ` Arjan van de Ven [this message]
2006-10-17 13:23 ` Jens Axboe
2006-10-17 14:37 ` Ric Wheeler
2006-10-17 14:47 ` Jens Axboe
2006-10-17 14:46 ` Phetteplace, Thad (GE Healthcare, consultant)
2006-10-18 8:00 ` Jakob Oestergaard
2006-10-18 9:40 ` Arjan van de Ven
2006-10-18 11:30 ` Jakob Oestergaard
2006-10-18 11:49 ` Jens Axboe
2006-10-18 12:23 ` Jakob Oestergaard
2006-10-18 12:42 ` Alan Cox
2006-10-18 12:44 ` Jens Axboe
2006-10-18 12:55 ` Nick Piggin
2006-10-18 13:04 ` Jens Axboe
2006-10-18 13:39 ` Jakob Oestergaard
2006-10-18 13:51 ` Paulo Marques
2006-10-19 12:22 ` Jens Axboe
2006-10-18 13:37 ` Jakob Oestergaard
2006-10-18 12:44 ` Jakob Oestergaard
2006-10-18 12:42 ` Jens Axboe
2006-10-18 13:35 ` Jakob Oestergaard
2006-10-18 9:51 ` Jens Axboe
2006-10-18 11:00 ` Helge Hafting
2006-10-18 11:14 ` Jens Axboe
2006-10-18 11:23 ` Ric Wheeler
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=1161048269.3245.26.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=Thad.Phetteplace@ge.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®