From: Con Kolivas <conman@kolivas.net>
To: "John Stoffel" <stoffel@lucent.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.43 with contest
Date: Thu, 17 Oct 2002 00:56:13 +1000 [thread overview]
Message-ID: <200210170056.16385.conman@kolivas.net> (raw)
In-Reply-To: <15789.31874.550728.696896@gargle.gargle.HOWL>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 17 Oct 2002 12:49 am, John Stoffel wrote:
> Con,
>
> Why are you bothering to show the older 2.5.3x series of kernels, but
> dropping the 2.4.18 results? Wouldn't it make sense to see how the
> latest kernels in each section were doing?
My main interest in doing these is to help 2.5 development as 2.4 is not
changing dramatically anywhere in the near future. As the number of data
points increase the ability to sift through the information will decrease.
The comparison to 2.4 kernels has been made in the past and I felt that
showing the progression of 2.5 would be more helpful as the change made by
each step could be quantified. I dont mind posting a full set of benchmarks
but people are less likely to read through a huge set of data trying to find
the relevant information. If someone feels I am in error I would be happy to
change what I'm doing.
Cheers,
Con.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9rX4NF6dfvkL3i1gRAq8oAJ9QwnsPvNx4P7MDZdDWJOonA/HDUgCfTKj3
hReHZbmbXsCjCkuEJwOrDpQ=
=lun1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-10-16 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 6:24 [BENCHMARK] 2.5.43 with contest Con Kolivas
2002-10-16 14:49 ` John Stoffel
2002-10-16 14:56 ` Con Kolivas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 19:11 Dieter Nützel
2002-10-17 2:04 ` Con Kolivas
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=200210170056.16385.conman@kolivas.net \
--to=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stoffel@lucent.com \
/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