From: Bharathi S <bharathi@lantana.tenet.res.in>
To: Cong <vo.chi.cong@is.titech.ac.jp>
Cc: GNC GCC <gcc-help@gcc.gnu.org>
Subject: Re: how to get the number of CPUs?
Date: Thu, 04 Jul 2002 05:30:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0207041756180.29743-100000@lantana.iitm.ernet.in> (raw)
In-Reply-To: <20020704.204551.21926862.vo.chi.cong@is.titech.ac.jp>
On Thu, 4 Jul 2002, Cong wrote:
> number of CPUs on each of them. So I want to get the number of CPUs
cpu info is avilable in /proc/cpuinfo file
if processor is 0 then No. of CPU is 1
Explore /proc dir you will more idea :)
Bye,
--
--==| Bharathi S | BSB-364 DONLab | IIT-Madras |==--
Friendship is enthroned on the strength
That always helps with utmost warmth.
*In Tirukkural of Holy Tamil poet Tiruvalluvar.
next prev parent reply other threads:[~2002-07-04 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1025766825.11142.ezmlm@gcc.gnu.org>
2002-07-04 4:45 ` Cong
2002-07-04 5:30 ` Bharathi S [this message]
[not found] <616BE6A276E3714788D2AC35C40CD18D6C01F7@whale.softwire.co.uk>
2002-07-04 5:52 ` Rupert Wood
2002-07-06 21:24 ` Cong
2002-07-13 8:00 ` Nix
2002-07-04 13:11 Dockeen
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=Pine.LNX.4.21.0207041756180.29743-100000@lantana.iitm.ernet.in \
--to=bharathi@lantana.tenet.res.in \
--cc=gcc-help@gcc.gnu.org \
--cc=vo.chi.cong@is.titech.ac.jp \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).