All of lore.kernel.org
 help / color / mirror / Atom feed
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 20:37:57 -0400	[thread overview]
Message-ID: <1035592677.734.4377.camel@phantasy> (raw)
In-Reply-To: <3DB9D789.4020101@sktc.net>

On Fri, 2002-10-25 at 19:45, David D. Hagood wrote:

> I would assert that, at least in the case of the P4, there IS a "major 
> core", as the 2 subcores share L1 and bus controller access, as well as 
> several other parts of the chip.
> 
> I beleive this is to some extent the case in the Power4 modules - that 
> each module contains resources shared by the execution units. However, I 
> might be full of it, and since there are plenty of @ibm.com's here I 
> expect to be corrected shortly....

You are entirely right :)

But argument for siblings vs. subcore is that in the context of the
processors displayed in /proc/cpuinfo known of them are "subscores" of
the other (and thus none of them are the "main core").

Some are just "siblings" in the same parent process package.  So given a
dual Xeon machine, you have 4 virtual processors, which are broken into
two sets of two siblings.  Those two sets are each part of the same
package.

	Robert Love


  reply	other threads:[~2002-10-26  0:31 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
2002-10-25 23:45 ` David D. Hagood
2002-10-26  0:37   ` Robert Love [this message]
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=1035592677.734.4377.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 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.