mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
	Robert Love <rml@tech9.net>, 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>,
	colpatch@us.ibm.com
Subject: Re: [PATCH] hyper-threading information in /proc/cpuinfo
Date: Fri, 25 Oct 2002 19:51:59 -0700	[thread overview]
Message-ID: <2964027205.1035575518@[10.10.2.3]> (raw)
In-Reply-To: <20021026004726.GC1676@werewolf.able.es>

>> 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  
>> 
> 
> Er, while you're at it, would it be worthy to add ad:
> 
> node:	x
> 
> for NUMA boxes ?

We also need to indicate other things here though, which is why
Matt Dobson implemented a more complete topology description
under driverfs. If you're really interested in that level of 
detail from userspace, you probably also want to know things 
like whether the evil twins share a TLB cache or L1/L2 cache.
I can't help feeling that's the more correct & complete solution
to the problem. His patches are in the latest -mm tree, and would
need some more work to be extended to hyperthreading, but that
seems like the better way (for 2.5 at least).

M.


  reply	other threads:[~2002-10-26  2:48 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
2002-10-26  0:47   ` J.A. Magallon
2002-10-26  2:51     ` Martin J. Bligh [this message]
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='2964027205.1035575518@[10.10.2.3]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@digeo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=chrisl@vmware.com \
    --cc=colpatch@us.ibm.com \
    --cc=davej@codemonkey.org.uk \
    --cc=jamagallon@able.es \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®