public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanna Linder <hannal@us.ibm.com>
To: Austin Gonyou <austin@digitalroadkill.net>, linux-kernel@vger.kernel.org
Cc: hannal@us.ibm.com
Subject: Re: Recent kernel SMP scalability Benchmark/White-paper References.
Date: Thu, 23 May 2002 16:34:39 -0700	[thread overview]
Message-ID: <3500000.1022196878@w-hlinder.des> (raw)
In-Reply-To: <1022193715.7292.74.camel@UberGeek>


Hi Austin,

	Check out http://lse.sourceforge.net
and	http://sourceforge.net/projects/lse

(lse= linux scalability effort)

That might be more information than you were looking for.
Another good resource is the lse mailing list at: 
lse-tech@lists.sourceforge.net

We have bi-weekly conference calls where anyone is welcome
to join and ask questions or report your work or whatever.

As a developer working on SMP scalability on Linux I would 
say it is getting better but we still have work to do. 

Hanna Linder
IBM Linux Technology Center


--On Thursday, May 23, 2002 17:41:55 -0500 Austin Gonyou <austin@digitalroadkill.net> wrote:

> I was looking around on google web, google groups, lkml digests,
> Intel.com, RedHat, SuSe, SGI.com, osdl.com, etc for some benchmarks of
> recent 2.4.x kernels, say 2.4.x > 16, with references to SMP scalability
> problems or successes, etc. Mainly centering around 4-way/8-way x86
> testing in terms of memory bandwidth/utilization, threading performance,
> etc. 
> 
> I've not found much in my search so far, and thought at this point it
> might be best to ask on this list to help shorten the search a bit, if
> possible. Of the documents I do have, they're more marketing based and
> not really *technology* based or touch very heavily as to generic
> benchmarking of a standard Linux kernel on SMP. 
> 
> I'm hoping to create a white-paper internally, and hopefully externally
> at some point, which can be maintained so others don't have to do the
> same arduous task of trying to find recent data as it pertains to said
> statistics. 
> 
> Any help as to recent documentation of this nature would be *overly*
> appreciated! 
> 
> In addition to this info, I'm trying to gather information as it
> pertains to the scalability of Linux kernels on 4/8-way x86 systems
> versus Solaris Sparc 4/8-way systems with measurements of the same
> statistics. 
> 
> I fear I'm searching for a document which does not exist. TIA.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2002-05-23 23:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23 22:41 Recent kernel SMP scalability Benchmark/White-paper References Austin Gonyou
2002-05-23 23:34 ` Hanna Linder [this message]
2002-05-24  4:04   ` Austin Gonyou
2002-05-24  6:15     ` Hanna V Linder
2002-05-24 16:32       ` Austin Gonyou
2002-05-24  0:23 ` Stephane Charette
2002-05-24  4:01   ` Austin Gonyou
     [not found] <200205240230.g4O2U97457880@saturn.cs.uml.edu>
2002-05-24  3:59 ` Austin Gonyou

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=3500000.1022196878@w-hlinder.des \
    --to=hannal@us.ibm.com \
    --cc=austin@digitalroadkill.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