public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <gilbertd@nospam.treblig.org>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Christoph Hellwig <hch@infradead.org>,
	Robert Love <rml@tech9.net>,
	"Kuppuswamy, Priyadarshini" <Priyadarshini.Kuppuswamy@compaq.com>,
	linux-kernel@vger.kernel.org
Subject: Re: system call for finding the number of cpus??
Date: Mon, 8 Apr 2002 23:02:39 +0100	[thread overview]
Message-ID: <20020408220239.GK612@gallifrey> (raw)
In-Reply-To: <20020408222742.A28352@infradead.org> <Pine.LNX.4.33.0204081735330.10199-100000@coffee.psychology.mcmaster.ca>

* Mark Hahn (hahn@physics.mcmaster.ca) wrote:
> > See http://people.nl.linux.org/~hch/cpuinfo/ for details.
> 
> egads.  "grep -ci bogo /proc/cpuinfo" then.

Hmm, cpuinfo is a very human readable file, I wouldn't use it to do
things like that.

I suggest /proc/stat whose format appears to be designed for machine
reading and which has a 'cpu0' and 'cpu1' line on this here dual
processor box; and from 2.4.x on it seems to have a cpu0 even on
uniprocessor; so I suggest:

grep "^cpu[0-9][0-9]* " /proc/stat

But I'd actually go and ask the CPU hotswap guys - they must have a way
of getting a handle on this (hey does that mean you might have cpu0,
cpu1, cpu3 .... ?)

Me thinks the format of these /proc files needs documenting - is there
anything already?

Dave

 ---------------- Have a happy GNU millennium! ----------------------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2002-04-08 22:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 21:18 system call for finding the number of cpus?? Kuppuswamy, Priyadarshini
2002-04-08 21:25 ` Robert Love
2002-04-08 21:27   ` Christoph Hellwig
2002-04-08 21:37     ` Mark Hahn
2002-04-08 22:02       ` Dr. David Alan Gilbert [this message]
2002-04-11 10:11         ` Rusty Russell
2002-04-08 21:58     ` H. Peter Anvin
2002-04-09 14:28       ` Vince Weaver
2002-04-08 21:51   ` J.A. Magallon
2002-04-08 22:59   ` David Ford
2002-04-08 21:56 ` Davide Libenzi
2002-04-08 21:58   ` J.A. Magallon
2002-04-08 22:08     ` Davide Libenzi
2002-04-09  1:12     ` Nicholas Miell
2002-04-09 15:37 ` Tigran Aivazian
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08 21:54 Kuppuswamy, Priyadarshini
2002-04-08 22:05 ` Davide Libenzi
2002-04-08 22:12 ` J.A. Magallon
2002-04-09  5:36   ` Bernd Eckenfels
2002-04-09 15:39 ` Tigran Aivazian

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=20020408220239.GK612@gallifrey \
    --to=gilbertd@nospam.treblig.org \
    --cc=Priyadarshini.Kuppuswamy@compaq.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=hch@infradead.org \
    --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