Date: Tue, 27 May 2003 16:46:12 -0700
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
Message-Id: <20030527164612.3249bfe5.akpm@digeo.com>
In-Reply-To: <20030527225519.GL32128@ca-server1.us.oracle.com>
References: <20030527225519.GL32128@ca-server1.us.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1298
Lines: 38

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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/