From: Andrew Morton <akpm@digeo.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>,
Nick Piggin <piggin@cyberone.com.au>
Subject: Re: WimMark I report for 2.5.70-mm1
Date: Tue, 27 May 2003 16:46:12 -0700 [thread overview]
Message-ID: <20030527164612.3249bfe5.akpm@digeo.com> (raw)
In-Reply-To: <20030527225519.GL32128@ca-server1.us.oracle.com>
Joel Becker <Joel.Becker@oracle.com> wrote:
>
> WimMark I report for 2.5.70
>
> Runs: 1005.78 958.80 947.23
>
> WimMark I report for 2.5.70-mm1
>
> Runs (deadline): 717.27 1064.57 1089.13
> Runs (anticipatory): 1342.93 1121.47 1330.42
> ...
> WimMark I run results are archived at
> http://oss.oracle.com/~jlbec/wimmark/wimmark_I.html
This is nuts. WimMark keeps on showing 2:1 swings in throughput when no
other test shows any variation at all. I simply do not know what to make
of it.
Your results would appear to indicate that the regression between
2.5.69-mm5 and 2.5.69-mm8 was actually due to something in Linus's tree,
and it is now in 2.5.70.
I have an interdiff here between the linus.patch from mm5 and mm8 and it
contains nothing very interesting.
It's at http://www.zip.com.au/~akpm/linux/patches/stuff/wimmark-interdiff.txt
The actual diff is at
http://www.zip.com.au/~akpm/linux/patches/stuff/wimmark-interdiff.patch.gz
There is the bio split stuff in ll_rw_blk.c, but that shouldn't matter.
Which device driver are you using?
next prev parent reply other threads:[~2003-05-27 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 22:55 Joel Becker
2003-05-27 23:46 ` Andrew Morton [this message]
2003-05-27 23:59 ` Nick Piggin
2003-05-28 0:02 ` Joel Becker
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=20030527164612.3249bfe5.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=Joel.Becker@oracle.com \
--cc=axboe@suse.de \
--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
all inboxes | Powered by JetHome®