From: paniscus@free.fr
To: linux-kernel@vger.kernel.org
Subject: 2.6.26 : Strange processor / core mapping with Intel Q6600
Date: Sat, 08 Aug 2009 23:52:37 +0200 [thread overview]
Message-ID: <1249768357.4a7df3a5a62f6@imp.free.fr> (raw)
Hello,
It seems that the cpu / core-id mapping has changed since vanilla 2.6.26 (also
2.6.26.8, 2.6.27.29) with an Intel Core 2 Quad Q6600.
With 2.6.25.20 I have a correct mapping :
Processor 0 <---> Core-id 0
Processor 1 <---> Core-id 1
Processor 2 <---> Core-id 2
Processor 3 <---> Core-id 3
With 2.6.26 :
I have a this strange mapping :
Processor 0 <---> Core-id 0
Processor 1 <---> Core-id 2
Processor 2 <---> Core-id 3
Processor 3 <---> Core-id 1
/proc/cpuinfo with 2.6.26 :
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
stepping : 11
cpu MHz : 1600.000
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
...
...
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
stepping : 11
cpu MHz : 1600.000
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
...
...
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
stepping : 11
cpu MHz : 1600.000
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
...
...
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
stepping : 11
cpu MHz : 1600.000
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
...
...
I would appreciate it if you could help me on this. Is it maybe already an known
issue ?
regards,
-Franck.
reply other threads:[~2009-08-08 21:53 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=1249768357.4a7df3a5a62f6@imp.free.fr \
--to=paniscus@free.fr \
--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®