All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [announce] linux kernel performance project launch at sourceforge.net
Date: 15 Jul 2005 00:18:03 +0200	[thread overview]
Message-ID: <p73y889kp5w.fsf@bragg.suse.de> (raw)
In-Reply-To: <200507142021.j6EKLPg04710@unix-os.sc.intel.com.suse.lists.linux.kernel>

"Chen, Kenneth W" <kenneth.w.chen@intel.com> writes:

> I'm pleased to announce that we have established a linux kernel
> performance project, hosted at sourceforge.net:
> 
> http://kernel-perf.sourceforge.net

That's very cool. Thanks a lot.

Would it be possible to add 2.4.30 numbers and perhaps one or two 
distro kernels (let's say RHEL3/4, SLES8/9) to the graphs 
as data points for comparison? These are all very tuned
kernels and would show where mainline is worse than them.

Also how did you run netperf? Locally or to some other machine? 
Perhaps that should be documented.

Some oprofile listings from a few of the test runs would be also nice.

-Andi

       reply	other threads:[~2005-07-14 23:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200507142021.j6EKLPg04710@unix-os.sc.intel.com.suse.lists.linux.kernel>
2005-07-14 22:18 ` Andi Kleen [this message]
2005-07-14 22:24   ` [announce] linux kernel performance project launch at sourceforge.net Chen, Kenneth W
2005-07-14 22:27     ` Andi Kleen
2005-07-15  5:19       ` randy_dunlap
2005-07-15 19:16 Chen, Kenneth W
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14 20:21 Chen, Kenneth W
2005-07-14 22:34 ` Alexey Dobriyan
2005-07-14 22:33   ` Chen, Kenneth W
2005-07-15  8:15 ` Paolo Ciarrocchi
2005-07-15 15:05 ` Al Boldi

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=p73y889kp5w.fsf@bragg.suse.de \
    --to=ak@suse.de \
    --cc=kenneth.w.chen@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.