From: Andrew Morton <akpm@zip.com.au>
To: Steven Cole <elenstev@mesatop.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Performance differences for recent kernels running forky test.
Date: Wed, 14 Aug 2002 12:36:00 -0700 [thread overview]
Message-ID: <3D5AB120.BB7700AB@zip.com.au> (raw)
In-Reply-To: 1029352630.14756.140.camel@spc9.esa.lanl.gov
Steven Cole wrote:
>
> I ran the following lots_of_forks.sh script for several kernels.
>
> http://people.nl.linux.org/~phillips/patches/lots_of_forks.sh
>
> ...
> 2.4.20-pre2 2.4.20-pre2-ac1 2.5.28 2.5.31
>
> 1 24.96 53.18 39.91 37.04
> 2 24.92 52.42 44.91 45.88
> 3 24.69 50.69 48.63 44.89
> 4 24.39 51.9 58.12 55.8
> 5 24.72 46.14 49.81 43.18
> 6 24.34 47.99 57.62 40.93
> 7 24.64 52.33 50.42 47.27
> 8 24.53 52.84 45 36.49
>
That's the page_add_rmap/page_remove_rmap thing. Could you retest
2.5.31 with
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.31/stuff-sent-to-linus/everything.gz
applied?
next prev parent reply other threads:[~2002-08-14 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 19:17 Performance differences for recent kernels running forky test Steven Cole
2002-08-14 19:36 ` Andrew Morton [this message]
2002-08-14 20:12 ` Steven Cole
2002-08-15 1:17 ` Alan Cox
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=3D5AB120.BB7700AB@zip.com.au \
--to=akpm@zip.com.au \
--cc=elenstev@mesatop.com \
--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