Anton wrote:
> We have a userspace visible change to the sched
> affinity API when the cpusets option is enabled.
Yup - on cpuset kernels, sched_setaffinity is constrained to CPUs in a
tasks cpuset. Also mbind and set_mempolicy are constrained to nodes in
the tasks cpuset.
This is a long standing, intentional part of the cpuset design.
Using udev isn't papering over it. It's reflecting the reasonable
preference and expectation on systems using hotplug/unplug that
the default cpuset dynamically reflect the current online maps,
not the static maps as they were at boot. And using udev is using
just the sort of mechanism one might expect to be used to adjust
the system when devices go on or off line.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]