All of lore.kernel.org
 help / color / mirror / Atom feed
From: chrisl@vmware.com
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, linux-kernel@vger.kernel.org
Subject: Re: How to get number of physical CPU in linux from user space?
Date: Fri, 25 Oct 2002 12:12:02 -0700	[thread overview]
Message-ID: <20021025191202.GD1397@vmware.com> (raw)
In-Reply-To: <F2DBA543B89AD51184B600508B68D4000EA170E9@fmsmsx103.fm.intel.com>

On Fri, Oct 25, 2002 at 11:54:53AM -0700, Nakajima, Jun wrote:
> Recent distributions or the AC tree has additional fields in /proc/cpu,
> which tell
> - physical package id
> - number of threads 
> for each CPU.

That is exactly what I am looking for.

> 
> Using this info, you should be able to detect it. The problem is that they
> are not using the same keywords. I'm asking them to make those fields
> consistent.

Cool. Any idea when will those feature come to stander linux kernel?

Thanks.

Chris



  parent reply	other threads:[~2002-10-25 19:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 18:54 How to get number of physical CPU in linux from user space? Nakajima, Jun
2002-10-25 19:09 ` [PATCH] " Robert Love
2002-10-25 19:13   ` Dave Jones
2002-01-16 19:35     ` Pavel Machek
2002-10-25 19:21     ` Robert Love
2002-10-25 20:03       ` chrisl
2002-10-25 21:13   ` Alan Cox
2002-10-25 19:12 ` chrisl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-25 19:05 Nakajima, Jun
2002-10-24 23:02 chrisl
2002-10-25  0:47 ` Andrew Walrond
2002-10-25  8:26 ` Gianni Tedesco
2002-10-25  8:27 ` Martin J. Bligh
2002-10-25 18:20   ` chrisl
2002-10-25 18:35     ` David T Hollis
2002-10-25 18:52     ` Martin J. Bligh
2002-10-25 12:38 ` Dave Jones
2002-10-25 19:07   ` chrisl

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=20021025191202.GD1397@vmware.com \
    --to=chrisl@vmware.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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.