From: Martin Knoblauch <knobi@knobisoft.de>
To: 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 09:52:02 -0800 (PST) [thread overview]
Message-ID: <681548.1013.qm@web32601.mail.mud.yahoo.com> (raw)
In-Reply-To: <1167235772.3281.3977.camel@laptopd505.fenrus.org>
>In article <1167235772.3281.3977.camel@xxxxxxxxxxxxxxxxxxxxx> you
wrote:
>> once your program (and many others) have such a check, then the next
>> step will be pressure on the kernel code to "fake" the old situation
>> when there is a processor where <vague criteria of the day> no
longer
>> holds. It's basically a road to madness :-(
>
> I agree that for HPC sizing a benchmark with various levels of
> parallelity are better. The question is, if the code in question
> only is for inventory reasons. In that case I would do something
> like x sockets, y cores and z cm threads.
>
> Bernd
For sizing purposes, doing benchmarks is the only way. For the purpose
of Ganglia the sockets/cores/threads info is purely for inventory. And
we are likely going to add the new information to our metrics.
But - we still need to find a way to extract the infor :-)
Cheers
Martin
PS: I have likely killed the CC this time. Sorry.
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
next prev parent reply other threads:[~2006-12-27 17:52 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
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 [this message]
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=681548.1013.qm@web32601.mail.mud.yahoo.com \
--to=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®