From: Andrew Morton <akpm@digeo.com>
To: Jens Axboe <axboe@suse.de>
Cc: kernel@kolivas.org, linux-kernel@vger.kernel.org, piggin@cyberone.com.au
Subject: Re: [BENCHMARK] 2.5.61-mm1 +/- as or cfq with contest
Date: Sun, 16 Feb 2003 02:43:21 -0800 [thread overview]
Message-ID: <20030216024321.7b5a570d.akpm@digeo.com> (raw)
In-Reply-To: <20030216095956.GA6612@suse.de>
Jens Axboe <axboe@suse.de> wrote:
>
> On Sun, Feb 16 2003, Con Kolivas wrote:
> > On Sun, 16 Feb 2003 08:51 pm, Jens Axboe wrote:
> > > On Sun, Feb 16 2003, Con Kolivas wrote:
> > > > Here are contest (http://contest.kolivas.org) results with osdl
> > > > (http://www.osdl.org) hardware for 2.5.61-mm1 with either the as i/o
> > > > scheduler or the cfq scheduler.
> > > >
> > > > io_load:
> > > > Kernel [runs] Time CPU% Loads LCPU% Ratio
> > > > 2.5.60-mm1 3 112 67.0 15.7 7.1 1.42
> > > > 2.5.61 2 143 52.4 32.9 13.3 1.81
> > > > 2.5.61-mm1 2 634 12.5 257.3 24.6 7.83
> > > > 2.5.61-mm1cfq 3 397 19.6 123.3 18.1 5.03
> > >
> > > These loo fishy, could be some other interaction. I'm consistently
> > > beating 2.5.60-mm1/2.5.61 on io_load here, but that is 2.5.61 base and
> > > not 2.5.61-mm1 base. Could be something odd happening there.
> >
> > I dont think they're fishy - taken in the mm1 context -. I have tested cfq3a
> > without mm1 and it does beat the baseline. See a previous email I posted with
> > it.
>
> I didn't mean that you have done something fishy, but that there's a
> fishy interaction between -mm + CFQ :)
>
It is the CPU scheduler patch. Con has eariler shown that this patch shoots
io_load in the head. 2.5.60-mm1 did not have that patch.
next prev parent reply other threads:[~2003-02-16 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 9:46 [BENCHMARK] 2.5.61-mm1 +/- as or cfq with contest Con Kolivas
2003-02-16 9:51 ` Jens Axboe
2003-02-16 9:53 ` Con Kolivas
2003-02-16 9:59 ` Jens Axboe
2003-02-16 10:43 ` Andrew Morton [this message]
2003-02-16 10:45 ` 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=20030216024321.7b5a570d.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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