public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Bubrouski <stan@ccs.neu.edu>
To: max@vortex.physik.uni-konstanz.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4 shocking (HT) benchmarking (wrong logic./phys. HT CPU distinction?)
Date: Tue, 26 Aug 2003 12:36:26 -0400	[thread overview]
Message-ID: <3F4B8C8A.2060805@ccs.neu.edu> (raw)
In-Reply-To: <200308261552.44541.max@vortex.physik.uni-konstanz.de>

max@vortex.physik.uni-konstanz.de wrote:
> Hello all you great Linux hackers,
> 
> in our fine physics group we recently bought a DUAL XEON P4 2666MHz, 2GB, with 
> hyper-threading support and I had the honour of making the thing work. In the 
> process I also did some benchmarking using two different kernels (stock 
> SuSE-8.2-Pro 2.4.20-64GB-SMP, and the latest and greatest vanilla 
> 2.6.0-test4). I benchmarked 
> 
> [1] kernel compiles (after 'cat'ting all files >/dev/null, into the buffer 
> cache) and 
> 
> [2] running time of a multi-threaded numerical simulation making extensive use 
> of FFTs, using the fftw.org library.
> 
> To cut the detailed story (below) short, the results puzzle me to a certain 
> extend: The physical/logical CPU distinction, which 2.6.0 is supposed to make 

I'm no kernel developer so take my opinion as worth more than
anyone else here (much less).  The new scheduler in the 2.6
kernels is still being tweaked by Con and Igno, et al.  But beyond
that there are several new ways to tweak the scheduler
designed to handled different loads, amounts of mem. etc...

Skimming the past few months of the mail list archives for
what to tweak and how may enhance the tasks you are currently
testing.  My $0.01 (I'm cheap like that).

-sb



  reply	other threads:[~2003-08-26 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 13:52 2.6.0-test4 shocking (HT) benchmarking (wrong logic./phys. HT CPU distinction?) max
2003-08-26 16:36 ` Stan Bubrouski [this message]
2003-08-26 18:50 ` Andy Isaacson
2003-08-26 19:12   ` Richard B. Johnson
2003-08-27 13:40     ` Andrew Theurer
2003-08-26 19:20 ` bill davidsen

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=3F4B8C8A.2060805@ccs.neu.edu \
    --to=stan@ccs.neu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@vortex.physik.uni-konstanz.de \
    /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