This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What *is* the API for sched_getaffinity? Should sched_getaffinity always succeed when using cpu_set_t?
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Mon, 22 Jul 2013 14:43:35 -0700 (PDT)
- Subject: Re: What *is* the API for sched_getaffinity? Should sched_getaffinity always succeed when using cpu_set_t?
- References: <51E42BFE dot 7000301 at redhat dot com> <51E4A0BB dot 2070802 at gmail dot com> <51E4A123 dot 9070001 at gmail dot com> <51E6F3ED dot 8000502 at redhat dot com> <51E6F956 dot 5050902 at gmail dot com> <51E714DE dot 6060802 at redhat dot com> <CAHGf_=oZW3kNA3V-9u+BZNs3tL3JKCsO2a0Q6f0iJzo=N4Wb8w at mail dot gmail dot com> <51E7B205 dot 3060905 at redhat dot com>
> I can fix the glibc manual. A 'configured' CPU is one that the OS
> can bring online.
Where do you get this definition, in the absence of a standard that
specifies _SC_NPROCESSORS_CONF? The only definition I've ever known for
_SC_NPROCESSORS_CONF is a value that's constant for at least the life of
the process (and probably until reboot) that is the upper bound for what
_SC_NPROCESSORS_ONLN might ever report. If the implementation for Linux is
inconsistent with that definition, then it's just a bug in the implementation.