From: Andi Kleen <andi@firstfloor.org>
To: Allan Menezes <amenezes007@sympatico.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HPL benchmarking linux kernel for shared memory performance.
Date: 22 Mar 2008 11:04:32 +0100 [thread overview]
Message-ID: <87ve3fgjm7.fsf@basil.nowhere.org> (raw)
In-Reply-To: <47E48575.7040009@sympatico.ca>
Allan Menezes <amenezes007@sympatico.ca> writes:
> from filling the register EAX with values above 0x03
> So I was seeing only 2 cores for a quad core in cat /proc/cpuinfo on
> all nodes giving me lousy performance for every kernel except some
> like 2.6.23.13 and 2.6.23.14.
You say some older kernels behaved better than newer ones in the two
core oversub configuration? That would be still an issue that should
be investigated. After all Linux should run well even with
oversubscribing on two cores.
-Andi
next prev parent reply other threads:[~2008-03-22 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 4:05 HPL benchmarking linux kernel for shared memory performance Allan Menezes
2008-03-22 10:04 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-16 5:38 Allan Menezes
2008-03-16 10:42 ` Marcin Slusarz
2008-03-16 18:13 ` Roger Heflin
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=87ve3fgjm7.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=amenezes007@sympatico.ca \
--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