linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bill Hartner <bhartner@austin.ibm.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andrew Morton <akpm@digeo.com>,
	Bill Hartner <hartner@austin.ibm.com>,
	linux-mm@kvack.org, lse-tech@lists.sourceforge.net
Subject: Re: VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35,and   2.5.35 + mm1
Date: Wed, 18 Sep 2002 11:10:30 -0500	[thread overview]
Message-ID: <3D88A575.D25CE720@austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209172219200.1857-100000@imladris.surriel.com>


Rik van Riel wrote:
> 
> On Tue, 17 Sep 2002, Andrew Morton wrote:
> > Bill Hartner wrote:
> > >
> > > I ran VolanoMark 2.1.2 under memory pressure to test rmap.
> > >                              ---------------

> > > 2.5.26 vs 2.5.26 + rmap patch
> > > -----------------------------
> > > It appears as though the page stealing decisions made when using the
> > > 2.5.26 rmap patch may not be as good as the baseline for this workload.
> > > There was more swap activity and idle time.
> >
> > Do you have similar results for 2.4 and 2.4-rmap?
> 
> If Bill is going to test this, I'd appreciate it if he could use
> rmap14a (or newer, if I've released it by the time he gets around
> to testing).
> 

Rik,

I will baseline on 2.4.19 and run both the 3GB and 4GB VoloanoMark test.

I will also test with rmap14a.

I am currently running (a) rawio on scsi devices and (b) direct io on scsi
devices for both read and readv on 2.5.35.  For this test, I am using an
8-way 700 Mhz with (4) IBM 4Mx controllers and 32 disks.

I should be able to get to the 2.4.19 VolanoMark tests by the end of the week.
Both rawio and VolanoMark test use the same machine.

Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-09-18 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 21:14 VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35, and " Bill Hartner
2002-09-17 22:32 ` Andrew Morton
2002-09-18  1:22   ` Rik van Riel
2002-09-18 16:10     ` Bill Hartner [this message]
2002-09-18 16:17       ` VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35,and " Rik van Riel
2002-09-18 18:42         ` [Lse-tech] Re: VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35,and2.5.35 " Bill Hartner
2002-09-27 17:00     ` VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35,and 2.5.35 " Bill Hartner
2002-09-27 18:32       ` Andrew Morton
2002-10-02 18:51         ` VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35 + mm1, and 2.5.38 + mm3 Bill Hartner
2002-10-02 19:36           ` Andrew Morton
2002-10-02 21:03             ` [Lse-tech] Re: VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35 +mm1, " Andrew Morton
2002-10-02 20:59           ` [Lse-tech] Re: VolanoMark Benchmark results for 2.5.26, 2.5.26 + rmap, 2.5.35 + mm1, " Dave Hansen
2002-10-03 13:59             ` [Lse-tech] Re: VolanoMark Benchmark results for 2.5.26, 2.5.26+ " Bill Hartner
2002-10-03 16:43               ` Andrew Morton

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=3D88A575.D25CE720@austin.ibm.com \
    --to=bhartner@austin.ibm.com \
    --cc=akpm@digeo.com \
    --cc=hartner@austin.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=riel@conectiva.com.br \
    /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