linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jon Masters <jcm@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jeff Burke <jburke@redhat.com>
Subject: Re: CPU siblings
Date: Thu, 20 Mar 2008 17:48:23 -0400	[thread overview]
Message-ID: <47E2DBA7.6050708@tmr.com> (raw)
In-Reply-To: <1206028996.5225.6.camel@jcmlaptop>

Jon Masters wrote:
> 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?
> 
Related topic: Intel has announced that some of their new CPU lines will 
once again have SMT in each core. Just the thought of multiple sockets 
with multiple core, with multiple threads and shared L3 cache sounds 
like a scheduling nightmare.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

      reply	other threads:[~2008-03-20 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 16:03 CPU siblings Jon Masters
2008-03-20 21:48 ` Bill Davidsen [this message]

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=47E2DBA7.6050708@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jburke@redhat.com \
    --cc=jcm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).