From: Andreas Jaeger <aj@suse.de>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: get_nprocs question
Date: Tue, 16 Mar 2004 06:23:00 -0000 [thread overview]
Message-ID: <m3brmxia3m.fsf@gromit.moeb> (raw)
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
What exactly is the semantics of get_nprocs, the manual states:
The @code{get_nprocs} function returns the number of available processors.
Does available mean the number of all processors the kernel runs on?
Or does it mean the number of CPUs upon which the process and its
children will be permitted to execute?
In the latter case we can use the sched_getaffinity system call for
get_nprocs if it's available. If this is ok, I'll prepare a patch...
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2004-03-16 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 6:23 Andreas Jaeger [this message]
2004-03-16 20:05 ` Andreas Jaeger
2004-03-16 20:12 ` Ulrich Drepper
2004-03-17 5:33 ` Andreas Jaeger
2004-03-17 5:50 ` Ulrich Drepper
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=m3brmxia3m.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.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 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).