From: "JA Magallón" <jamagallon@ono.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Inconsistency in /proc/cpuinfo about topology ?
Date: Fri, 14 Sep 2012 15:37:18 +0200 [thread overview]
Message-ID: <5053330E.80003@ono.com> (raw)
Hi...
Probably there is something I don't understand, but it looks to me like an
inconsistency in the info given by /proc/cpuinfo about processor/core/thread
topology.
For new processors, data seems to account for each 'physycal id', all virtual
processors in the same package repeat the same info:
- Core i5:
physical id : 0
siblings : 4
cpu cores : 4
- Core i3:
physical id : 0
siblings : 4
cpu cores : 2
- Dual Xeon X5365
physical id : 0
siblings : 4
cpu cores : 4
physical id : 1
siblings : 4
cpu cores : 4
- Core Q9450
physical id : 0
siblings : 4
cpu cores : 4
but for older CPUs or lower end it is not the same:
- Dual P4-Xeon:
physical id : 0
siblings : 1
cpu cores : 1
physical id : 0
siblings : 1
cpu cores : 0
physical id : 3
siblings : 1
cpu cores : 1
physical id : 3
siblings : 1
cpu cores : 0
- Single P4 HT:
physical id : 0
siblings : 1
cpu cores : 1
physical id : 0
siblings : 1
cpu cores : 0
What am I missing ?
TIA
--
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
reply other threads:[~2012-09-14 14:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5053330E.80003@ono.com \
--to=jamagallon@ono.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.