[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091002172842.GA4884@elte.hu>
Date: Fri, 2 Oct 2009 19:28:42 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Mike Galbraith <efault@....de>,
Vivek Goyal <vgoyal@...hat.com>,
Ulrich Lukas <stellplatz-nr.13a@...enparkplatz.de>,
linux-kernel@...r.kernel.org,
containers@...ts.linux-foundation.org, dm-devel@...hat.com,
nauman@...gle.com, dpshah@...gle.com, lizf@...fujitsu.com,
mikew@...gle.com, fchecconi@...il.com, paolo.valente@...more.it,
ryov@...inux.co.jp, fernando@....ntt.co.jp, jmoyer@...hat.com,
dhaval@...ux.vnet.ibm.com, balbir@...ux.vnet.ibm.com,
righi.andrea@...il.com, m-ikeda@...jp.nec.com, agk@...hat.com,
akpm@...ux-foundation.org, peterz@...radead.org,
jmarchan@...hat.com, riel@...hat.com
Subject: Re: IO scheduler based IO controller V10
* Jens Axboe <jens.axboe@...cle.com> wrote:
> On Fri, Oct 02 2009, Ingo Molnar wrote:
> >
> > * Jens Axboe <jens.axboe@...cle.com> wrote:
> >
> > > It's not _that_ easy, it depends a lot on the access patterns. A
> > > good example of that is actually the idling that we already do.
> > > Say you have two applications, each starting up. If you start them
> > > both at the same time and just care for the dumb low latency, then
> > > you'll do one IO from each of them in turn. Latency will be good,
> > > but throughput will be aweful. And this means that in 20s they are
> > > both started, while with the slice idling and priority disk access
> > > that CFQ does, you'd hopefully have both up and running in 2s.
> > >
> > > So latency is good, definitely, but sometimes you have to worry
> > > about the bigger picture too. Latency is more than single IOs,
> > > it's often for complete operation which may involve lots of IOs.
> > > Single IO latency is a benchmark thing, it's not a real life
> > > issue. And that's where it becomes complex and not so black and
> > > white. Mike's test is a really good example of that.
> >
> > To the extent of you arguing that Mike's test is artificial (i'm not
> > sure you are arguing that) - Mike certainly did not do an artificial
> > test - he tested 'konsole' cache-cold startup latency, such as:
>
> [snip]
>
> I was saying the exact opposite, that Mike's test is a good example of
> a valid test. It's not measuring single IO latencies, it's doing a
> sequence of valid events and looking at the latency for those. It's
> benchmarking the bigger picture, not a microbenchmark.
Good, so we are in violent agreement :-)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists