From: Arjan van de Ven <arjan@infradead.org>
To: knobi@knobisoft.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to detect multi-core and/or HT-enabled CPUs in 2.4.x and 2.6.x kernels
Date: Wed, 27 Dec 2006 16:13:00 +0100 [thread overview]
Message-ID: <1167232380.3281.3938.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <927934.92732.qm@web32603.mail.mud.yahoo.com>
>
> one piece of information that Ganglia collects for a node is the
> "number of CPUs", originally meaning "physical CPUs".
Ok I was afraid of that.
> With the
> introduction of HT and multi-core things are a bit more complex now. We
> have decided that HT sibblings do not qualify as "real" CPUs, while
> multi-cores do.
I think that decision is a mistake, and is probably based on experiences
with the first generation of HT capable Pentium 4 processors.
The original p4 HT to a large degree suffered from a too small cache
that now was shared. SMT in general isn't per se all that different in
performance than dual core, at least not on a fundamental level, it's
all a matter of how many resources each thread has on average. With dual
core sharing the cache for example, that already is part HT. Putting the
"boundary" at HT-but-not-dual-core is going to be highly artificial and
while it may work for the current hardware, in general it's not a good
way of separating things (just look at the PowerPC processors, those are
highly SMT as well), and I suspect that your distinction is just going
to break all the time over the next 10 years ;) Or even today on the
current "large cache" P4 processors with HT it already breaks. (just
those tend to be the expensive models so more rare)
I would strongly urge you to reconsider this decision; if you want to
show "sockets" that sounds reasonable, or even if you want to do it on
the "bus sharing" level (FSB/HT), but HT.. just sounds wrong.
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-12-27 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 14:16 Martin Knoblauch
2006-12-27 14:24 ` Arjan van de Ven
2006-12-27 14:40 ` Martin Knoblauch
2006-12-27 15:13 ` Arjan van de Ven [this message]
2006-12-27 15:22 ` Gleb Natapov
2006-12-27 15:38 ` Arjan van de Ven
2006-12-27 15:41 ` Martin Knoblauch
2006-12-27 15:53 ` Arjan van de Ven
2006-12-27 15:51 ` Martin Knoblauch
2006-12-27 16:09 ` Arjan van de Ven
2006-12-27 17:14 ` Bernd Eckenfels
2006-12-27 17:52 ` Martin Knoblauch
2006-12-27 19:58 ` Siddha, Suresh B
2006-12-27 14:37 ` Jan Engelhardt
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=1167232380.3281.3938.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=knobi@knobisoft.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
all inboxes | Powered by JetHome®