From: Robert Love <rml@tech9.net>
To: "David D. Hagood" <wowbagger@sktc.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Daniel Phillips <phillips@arcor.de>,
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: 25 Oct 2002 19:25:09 -0400 [thread overview]
Message-ID: <1035588310.734.4165.camel@phantasy> (raw)
In-Reply-To: <3DB9D1FE.5010607@sktc.net>
On Fri, 2002-10-25 at 19:21, David D. Hagood wrote:
> Might I suggest "subcore", since that's really what it is - a sub-core
> in the main chip.
>
> My siblings are distinct entities from me, my sub-parts aren't.
> (now, were I part of a cojoined twin....)
Sibling makes sense if you look at the N processors in the package as
"siblings of each other" i.e. not a hierarchy (as subcore implies) but
just a "set of virtual processors in the same core".
If there are subcores, then I think there must be some major core. If
two chips are siblings, then that merely says they are related (in this
case, the same parent package).
Robert Love
next prev parent reply other threads:[~2002-10-25 23:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 22:42 [PATCH] hyper-threading information in /proc/cpuinfo Nakajima, Jun
2002-10-25 22:57 ` Jeff Garzik
2002-10-25 23:21 ` David D. Hagood
2002-10-25 23:25 ` Robert Love [this message]
2002-10-25 23:45 ` David D. Hagood
2002-10-26 0:37 ` Robert Love
2002-10-25 23:51 ` Daniel Phillips
-- 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:59 Nakajima, Jun
2002-10-26 0:43 ` J.A. Magallon
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
2002-10-25 23:24 Nakajima, Jun
2002-10-25 23:45 ` Jeff Garzik
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=1035588310.734.4165.camel@phantasy \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisl@vmware.com \
--cc=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=phillips@arcor.de \
--cc=wowbagger@sktc.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