public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: ak@suse.de
Subject: sched_domains and Stream benchmark
Date: Tue, 20 Apr 2004 10:43:17 -0700	[thread overview]
Message-ID: <1082482996.2711.17.camel@farah> (raw)

Andi,

You have mentioned the stream benchmark when reporting on the
performance of the Opteron NUMA sched-domains scheduler.  I am trying to
reproduce your results and am struggling with the benchmark.  Can you
rpovide the details of the tests you ran.  Namely your compiler
settings, compile command line, and your value of N.  Also I didn't see
how to specify the number of threads to run, how did you specify that? 
I have a 4 way 1.4 GHz 1MB cache opteron machine with 7 GB of RAM.

When I ran the steeam_omp benchmark with N=4000000 I got nearly
identical results (within statistical noise) from 2.6.5, 2.6.5-mm5, and
2.6.5-mm5-with_flat_domains (the patch I sent earlier).  Clearly not
what is expected, so I assume I am not running or building the benchmark
correctly.  I found the projects build system (none) and docs (minimal)
to be lacking.

You mentioned your problem was fixed by some of "Ingo's tweaks".  Which
patches are these tweaks in and are they in the mm tree yet?

Thanks,

Darren


             reply	other threads:[~2004-04-20 17:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 17:43 Darren Hart [this message]
     [not found] <1N7xQ-7fh-29@gated-at.bofh.it>
2004-04-20 18:58 ` sched_domains and Stream benchmark Andi Kleen
2004-04-26 22:30   ` Darren Hart
2004-04-27  2:33     ` Andi Kleen
2004-04-27  2:44       ` Nick Piggin
2004-04-27  2:48         ` Andi Kleen
2004-04-27  2:54           ` Ingo Molnar
2004-04-27 16:47       ` Darren Hart
2004-04-27 21:03         ` Andi Kleen
2004-04-28  9:47     ` Zoltan Menyhart
2004-04-28 17:20       ` Andi Kleen

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=1082482996.2711.17.camel@farah \
    --to=dvhltc@us.ibm.com \
    --cc=ak@suse.de \
    --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