From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jakob Oestergaard <jakob@unthought.net>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Arjan van de Ven <arjan@infradead.org>,
"Phetteplace, Thad (GE Healthcare,
consultant)" <Thad.Phetteplace@ge.com>,
linux-kernel@vger.kernel.org
Subject: Re: Bandwidth Allocations under CFQ I/O Scheduler
Date: Wed, 18 Oct 2006 13:42:24 +0100 [thread overview]
Message-ID: <1161175344.9363.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20061018122323.GW23492@unthought.net>
Ar Mer, 2006-10-18 am 14:23 +0200, ysgrifennodd Jakob Oestergaard:
> iops/sec is what you get from your disks. In real world scenarios. It's
> no more magic than the real world, and no harder to understand than real
> world disks. Although I admit real-world disks can be a bitch at times ;)
Even iops/sec is very vague and arbitary. If your disk happens to be
retrying a sector or doing a cleaning pass or any other housekeeping or
vibration damping and so on you'll get very different numbers.
Bandwidth is completely silly in this context, iops/sec is merely
hopeless 8)
next prev parent reply other threads:[~2006-10-18 12:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 20:46 Bandwidth Allocations under CFQ I/O Scheduler Phetteplace, Thad (GE Healthcare, consultant)
2006-10-17 1:24 ` Arjan van de Ven
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 [this message]
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=1161175344.9363.30.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Thad.Phetteplace@ge.com \
--cc=arjan@infradead.org \
--cc=jakob@unthought.net \
--cc=jens.axboe@oracle.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