From: Roy Dragseth <Roy.Dragseth@cc.uit.no>
To: linux-ia64@vger.kernel.org
Subject: Probing for physical number of cpus.
Date: Fri, 28 Oct 2005 11:18:51 +0000 [thread overview]
Message-ID: <200510281318.51532.Roy.Dragseth@cc.uit.no> (raw)
Hi.
Do anyone know how to figure out the physical number of cpus in an ia64
system? No, /proc/cpuinfo wont do because the kernel is booted with
maxcpus=1.
When installing RH EL the install kernel is booted with maxcpus=1 and I need
to figure out the physical number of cpus in the system for later use in the
software setup. I need to be able to get this from userspace.
Any hints is greatly appreciated.
Regards,
r.
--
The Computer Center, University of Tromsø, N-9037 TROMSØ Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, High Performance Computing System Administrator
Direct call: +47 77 64 62 56. email: royd@cc.uit.no
next reply other threads:[~2005-10-28 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 11:18 Roy Dragseth [this message]
2005-10-28 12:43 ` Probing for physical number of cpus Andreas Schwab
2005-11-03 8:10 ` Roy Dragseth
2005-11-03 21:06 ` Ashok Raj
2005-11-07 10:20 ` Roy Dragseth
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=200510281318.51532.Roy.Dragseth@cc.uit.no \
--to=roy.dragseth@cc.uit.no \
--cc=linux-ia64@vger.kernel.org \
/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