get_nprocs question

[Andreas Jaeger]

Ulrich Drepper <drepper@redhat.com> writes:

> Andreas Jaeger wrote:
>
>> Here's the proposed patch.  Is this ok?
>
> No.  The value returned never had a thread-specific value but with
> getaffinity it would have.  The definition should stay as it it, the
> affinity issue reducing the possible number of processors the
> process/thread can run on is a different issue which needs a different
> set of interfaces.

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;

How can configured be different from available?  My change above would
make it different but perhaps not as desired...

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-hacker/attachments/20040317/73156b61/attachment.sig>