From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: get_nprocs question
Date: Wed, 17 Mar 2004 05:50:00 -0000 [thread overview]
Message-ID: <4057E726.1060201@redhat.com> (raw)
In-Reply-To: <m34qsoghqo.fsf@gromit.moeb>
Andreas Jaeger wrote:
> OK, then just one more question: What is the difference between these
> two:
>
> /* Return number of configured processors. */
> extern int get_nprocs_conf (void) __THROW;
>
> /* Return number of available processors. */
> extern int get_nprocs (void) __THROW;
The number of processors the OS knows or knew about need not be the same
as the number which is currently in use by any process. This is all
from long before there was affinity. Processors can be disabled (think
hotplug). The SPARC kernel always had the distinction, x86 and may
others don't.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
prev parent reply other threads:[~2004-03-17 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 6:23 Andreas Jaeger
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 [this message]
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=4057E726.1060201@redhat.com \
--to=drepper@redhat.com \
--cc=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).