From: "J.A. Magallon" <jamagallon@able.es>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Robert Love <rml@tech9.net>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"'Dave Jones'" <davej@codemonkey.org.uk>,
"'akpm@digeo.com'" <akpm@digeo.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'chrisl@vmware.com'" <chrisl@vmware.com>,
"'Martin J. Bligh'" <mbligh@aracnet.com>
Subject: Re: [PATCH] hyper-threading information in /proc/cpuinfo
Date: Sat, 26 Oct 2002 02:43:20 +0200 [thread overview]
Message-ID: <20021026004320.GA1676@werewolf.able.es> (raw)
In-Reply-To: <F2DBA543B89AD51184B600508B68D4000ECE70C8@fmsmsx103.fm.intel.com>; from jun.nakajima@intel.com on Sat, Oct 26, 2002 at 01:59:29 +0200
On 2002.10.26 "Nakajima, Jun" wrote:
>RedHat 8.0 is using
> "Physical processor ID\t:"
> "Number of siblings\t:"
>This implies they need to change it anyway, because 2.4-ac is
> "physical id\t:"
> "siblings\t:"
>
Summary:
- we have processor packages
- each package can handle several (someone said 128+ ;) ) processor cores.
We really do not mind if they are really independent (power4) or not
(xeon, ht)
- each core is a logical unit for Linux
- can we have two packages with different number of cores ?
Proposal for /proc/cpuinfo (sample box: an hypothetical TurboPower4 with
4 cores, 2 units on an SMP box):
processor : 0 processor : 2 processor : 4 processor : 6
package : 0 package : 0 package : 0 package : 0
core : 0 core : 1 core : 2 core : 3
processor : 1 processor : 3 processor : 5 processor : 7
package : 1 package : 1 package : 1 package : 1
core : 0 core : 1 core : 2 core : 3
So you can look for siblings based on package number, you can know if
two precessors are in different packages (for sched...), etc.
NOTE: do not know if 'core' name can give problems, perhaps you could use
'unit' instead.
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.20-pre11-jam2 (gcc 3.2 (Mandrake Linux 9.0 3.2-2mdk))
next prev parent reply other threads:[~2002-10-26 0:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 23:59 Nakajima, Jun
2002-10-26 0:43 ` J.A. Magallon [this message]
2002-10-26 0:47 ` J.A. Magallon
2002-10-26 2:51 ` Martin J. Bligh
2002-10-26 19:48 ` Rik van Riel
2002-10-28 18:53 ` chrisl
2002-10-28 21:54 ` J.A. Magallon
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 22:36 Nakajima, Jun
2002-10-26 1:58 Nakajima, Jun
2002-10-26 0:54 Nakajima, Jun
2002-10-26 0:26 Nakajima, Jun
2002-10-25 23:24 Nakajima, Jun
2002-10-25 23:45 ` Jeff Garzik
2002-10-25 22:42 Nakajima, Jun
2002-10-25 22:57 ` Jeff Garzik
2002-10-25 23:21 ` David D. Hagood
2002-10-25 23:25 ` Robert Love
2002-10-25 23:45 ` David D. Hagood
2002-10-26 0:37 ` Robert Love
2002-10-25 23:51 ` Daniel Phillips
2002-10-25 21:50 Nakajima, Jun
2002-10-25 21:54 ` Robert Love
2002-10-25 22:19 ` chrisl
2002-10-25 22:14 ` Alan Cox
2002-10-25 22:06 ` Daniel Phillips
2002-10-25 22:10 ` Robert Love
2002-10-25 22:25 ` Jeff Garzik
2002-10-26 0:49 ` Rik van Riel
2002-10-26 15:45 ` Eric W. Biederman
2002-10-25 20:38 [PATCH] How to get number of physical CPU in linux from user space? Nakajima, Jun
2002-10-25 21:30 ` [PATCH] hyper-threading information in /proc/cpuinfo Robert Love
2002-10-25 21:39 ` Robert Love
2002-10-26 0:01 ` Dave Jones
2002-10-26 0:04 ` Jeff Garzik
2002-10-26 0:12 ` Dave Jones
2002-10-26 0:16 ` Jeff Garzik
2002-10-26 0:33 ` Robert Love
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=20021026004320.GA1676@werewolf.able.es \
--to=jamagallon@able.es \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisl@vmware.com \
--cc=davej@codemonkey.org.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=rml@tech9.net \
/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
Powered by JetHome