From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <ak@suse.de>
Cc: dvhltc@us.ibm.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, mjbligh@us.ibm.com, ricklind@us.ibm.com,
akpm@osdl.org
Subject: Re: 2.6.5-rc3-mm4 x86_64 sched domains patch
Date: Thu, 15 Apr 2004 15:51:41 +1000 [thread overview]
Message-ID: <407E22ED.6050802@yahoo.com.au> (raw)
In-Reply-To: <20040414164135.75f1856f.ak@suse.de>
Andi Kleen wrote:
> On Thu, 15 Apr 2004 00:14:19 +1000
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>>Where is STREAM versus other kernels? You said you got
>>best performance on a custom 2.4 kernel. Do we match
>>that?
>
>
> Differences were below the measurement error, so I consider it fixed.
>
great.
>
>>How is your performance for other things? I recall you
>>may have told me about some other (smaller) issues you
>>were seeing?
>
>
> I haven't tested much yet. I can compare kernel compilations later.
>
That would be good. I don't expect you to do all the work,
but Opteron being a non traditional NUMA, and me doing most
of my testing on an old NUMAQ makes them quite important.
Even if you just got some results for a couple of random
benchmarks would be great.
> Also I'm still somewhat hoping that the IBM benchmark team will take a stab at
> it - they are much better than me at running many tests.
>
Well we've survived OSDL's STP tests as far as I know. A
couple of regressions were found and fixed there, so that
was good.
next prev parent reply other threads:[~2004-04-15 5:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 23:22 2.6.5-rc3-mm4 x86_64 sched domains patch Darren Hart
2004-04-08 23:42 ` Nick Piggin
2004-04-11 8:57 ` shai
2004-04-11 9:57 ` Rick Lindsley
2004-04-11 15:07 ` Martin J. Bligh
2004-04-14 13:44 ` Andi Kleen
2004-04-14 14:14 ` Nick Piggin
2004-04-14 14:41 ` Andi Kleen
2004-04-15 5:51 ` Nick Piggin [this message]
2004-04-14 17:24 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2004-04-14 23:20 Siddha, Suresh B
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=407E22ED.6050802@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjbligh@us.ibm.com \
--cc=ricklind@us.ibm.com \
/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.