From: Andrew Morton <akpm@digeo.com>
To: Con Kolivas <conman@kolivas.net>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: [BENCHMARK] 2.5.39 with contest 0.41
Date: Sat, 28 Sep 2002 01:45:53 -0700 [thread overview]
Message-ID: <3D956C41.E2EB78FB@digeo.com> (raw)
In-Reply-To: 1033201873.3d9568d158a72@kolivas.net
Con Kolivas wrote:
>
> ...
> Ok will fix. But please Andrew use version 0.41 of contest (posted only 2 hours
> ago). The results from that are far more meaningful and reproducible.
>
I am doing. I just tested for the "proces load" variation which
you saw (I assume that's what the test calls "CPU load"). With
and without the -mm patches:
cpuload 2:31.55 297%
cpuload 2:31.75 295%
So... Maybe some extra samples would be needed there.
next prev parent reply other threads:[~2002-09-28 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 6:58 [BENCHMARK] 2.5.39 with contest 0.41 Con Kolivas
2002-09-28 8:23 ` Andrew Morton
2002-09-28 8:31 ` Con Kolivas
2002-09-28 8:45 ` Andrew Morton [this message]
2002-09-28 9:08 ` Jens Axboe
2002-09-28 9:17 ` Con Kolivas
2002-09-28 15:17 Paolo Ciarrocchi
2002-09-28 23:59 ` Con Kolivas
2002-09-29 9:00 Paolo Ciarrocchi
2002-09-29 9:17 ` Con Kolivas
2002-09-29 17:14 Paolo Ciarrocchi
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=3D956C41.E2EB78FB@digeo.com \
--to=akpm@digeo.com \
--cc=axboe@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).