public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Bubrouski <stan@ccs.neu.edu>
To: Robert Love <rml@ufl.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: Tue, 10 Dec 2002 15:02:26 -0500	[thread overview]
Message-ID: <3DF64852.9030006@ccs.neu.edu> (raw)
In-Reply-To: <1039545941.1831.849.camel@phantasy>

Robert Love wrote:
> 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.

I disagree, 2.4.20 is the current stable kernel, it would
be nice to see how it compares to the current development,
what's faster, what's not... from Con's previous results
we can see that some things are indeed not as fast in 2.5.x
as in 2.4.x.  It's just nice to be able to see the whole
picture.  I often follow these threads for just this purpose.

-Stan

> 
> 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
> 




  reply	other threads:[~2002-12-10 19:54 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
2002-12-10 20:02     ` Stan Bubrouski [this message]
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=3DF64852.9030006@ccs.neu.edu \
    --to=stan@ccs.neu.edu \
    --cc=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ufl.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