mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Martin Knoblauch <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 11:58:55 -0800	[thread overview]
Message-ID: <20061227115854.C23645@unix-os.sc.intel.com> (raw)
In-Reply-To: <681548.1013.qm@web32601.mail.mud.yahoo.com>; from knobi@knobisoft.de on Wed, Dec 27, 2006 at 09:52:02AM -0800

On Wed, Dec 27, 2006 at 09:52:02AM -0800, Martin Knoblauch wrote:
>  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 :-)

Only the 2.4 x86_64 kernels are exporting limited info("physical id",
"siblings") through /proc/cpuinfo.

Some of the distos based on 2.4 kernels have the complete topology
(physical id, core id, cpu cores, siblings) exported through /proc/cpuinfo.

thanks,
suresh

  reply	other threads:[~2006-12-27 20:27 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
2006-12-27 19:58               ` Siddha, Suresh B [this message]
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=20061227115854.C23645@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --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®