From: Jon Masters <jcm@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jeff Burke <jburke@redhat.com>
Subject: CPU siblings
Date: Thu, 20 Mar 2008 12:03:16 -0400 [thread overview]
Message-ID: <1206028996.5225.6.camel@jcmlaptop> (raw)
Yo,
Myself and a colleague were just discussing the output of /proc/cpuinfo,
specifically the CPU siblings field. He pointed out/we think that this
historically was supposed to be number of HT siblings for a given CPU.
The actual value of that field comes from the Hamming Weight (number of
set bits) of the per_cpu cpu_core_map variable, which supposedly is
"representing HT and core siblings of each logical CPU", i.e. both HT
siblings and additional cores within the same CPU package.
Does this mean that "siblings" needs renaming? (doesn't it come
originally from "HT siblings"? or is it supposed to be both?). More
importantly, what's the correct way to determine number of HTs?
Jon.
next reply other threads:[~2008-03-20 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 16:03 Jon Masters [this message]
2008-03-20 21:48 ` CPU siblings Bill Davidsen
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=1206028996.5225.6.camel@jcmlaptop \
--to=jcm@redhat.com \
--cc=jburke@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.