mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 15:24:30 +0100	[thread overview]
Message-ID: <1167229470.3281.3905.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <666716.84435.qm@web32603.mail.mud.yahoo.com>

On Wed, 2006-12-27 at 06:16 -0800, Martin Knoblauch wrote:
> Hi, (please CC on replies, thanks)
> 
>  for the ganglia project (http://ganglia.sourceforge.net/) we are
> trying to find a heuristics to determine the number of physical CPU
> "cores" as opposed to virtual processors added by enabling HT. The
> method should work on 2.4 and 2.6 kernels.

I have a counter question for you.. what are you trying to do with the
"these two are SMT sibblings" information ?

Because I suspect "HT" is the wrong level of detection for what you
really want to achieve....

If you want to decide "shares caches" then at least 2.6 kernels directly
export that (and HT is just the wrong way to go about this). 
-- 
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


  reply	other threads:[~2006-12-27 14:24 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 [this message]
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
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=1167229470.3281.3905.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®