From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@digeo.com>
Cc: Con Kolivas <conman@kolivas.net>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.59-mm8 with contest
Date: Thu, 06 Feb 2003 12:02:27 +1100 [thread overview]
Message-ID: <3E41B423.2080309@cyberone.com.au> (raw)
In-Reply-To: 3E417624.2762A635@digeo.com
Andrew Morton wrote:
>Con Kolivas wrote:
>
>>..
>>
>>This seems to be creeping up to the same as 2.5.59
>>...
>>and this seems to be taking significantly longer
>>...
>>And this load which normally changes little has significantly different
>>results.
>>
>>
>
>There were no I/O scheduler changes between -mm7 and -mm8. I
>demand a recount!
>
It would suggest process scheduler changes are making the
difference.
next prev parent reply other threads:[~2003-02-06 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 11:21 [BENCHMARK] 2.5.59-mm8 with contest Con Kolivas
2003-02-05 20:37 ` Andrew Morton
2003-02-06 1:02 ` Nick Piggin [this message]
2003-02-06 8:08 ` Con Kolivas
2003-02-07 8:22 ` Andrew Morton
2003-02-07 10:26 ` Con Kolivas
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=3E41B423.2080309@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@digeo.com \
--cc=conman@kolivas.net \
--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