From: Robert Love <rml@ufl.edu>
To: Stan Bubrouski <stan@ccs.neu.edu>
Cc: Con Kolivas <conman@kolivas.net>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.51 with contest
Date: 10 Dec 2002 13:45:42 -0500 [thread overview]
Message-ID: <1039545941.1831.849.camel@phantasy> (raw)
In-Reply-To: <3DF621D0.6040505@ccs.neu.edu>
On Tue, 2002-12-10 at 12:18, Stan Bubrouski wrote:
> I know this has been brought up before, but
> these don't seem to mean much unless you
> include 2.4.20 in the comaprison.
Comparing this to 2.4 achieves nothing because so much changed.
The point of these benchmarks are not marketing, but to find
improvements or regressions from one version to the next and find out
what caused them.
Comparing the kernel to 2.4 has some uses (i.e. finding micro-ops) but
Con's mission is much different (and imo more useful).
Robert Love
next prev parent reply other threads:[~2002-12-10 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 11:44 [BENCHMARK] 2.5.51 with contest Con Kolivas
2002-12-10 17:18 ` Stan Bubrouski
2002-12-10 18:45 ` Robert Love [this message]
2002-12-10 20:02 ` Stan Bubrouski
2002-12-10 20:51 ` Arador
2002-12-10 21:05 ` Robert Love
2002-12-10 20:24 ` 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=1039545941.1831.849.camel@phantasy \
--to=rml@ufl.edu \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stan@ccs.neu.edu \
/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