On Sat, Nov 15, 2008 at 2:41 PM, Loic Domaigne <tech@xxxxxxxxxxxx> wrote: > Hi Michael! > > Looks good to me. I have only one minor comment left, regarding EINVAL for > pthread_setaffinity_np(): > >> .TP >> .BR EINVAL >> .RB ( pthread_setaffinity_np ()) >> .I cpuset >> specified a CPU that was outside the set supported by the kernel. >> (The kernel configuration option >> .BR CONFIG_NR_CPUS >> defines the range of the set supported by the kernel data type >> .\" cpumask_t >> used to represent CPU sets.) >> .\" The raw sched_getaffinity() system call returns the size (in bytes) >> .\" of the cpumask_t type. > > In the light of Bert's comment, it seems that the Linux kernel folks wants > to make the cpumask_t dynamic. So CONFIG_NR_CPUS might become obsolete in > the future... > > But for now, your explanation is fine. Okay. Thanks for the info Loic. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
