On Thu, 25 Oct 2007, David Rientjes wrote:
> Adds a new 'interleave_over_allowed' option to cpusets.
>
> When a task with an MPOL_INTERLEAVE memory policy is attached to a cpuset
> with this option set, the interleaved nodemask becomes the cpuset's
> mems_allowed. When the cpuset's mems_allowed changes, the interleaved
> nodemask for all tasks with MPOL_INTERLEAVE memory policies is also
> updated to be the new mems_allowed nodemask.
>
> This allows applications to specify that they want to interleave over all
> nodes that they are allowed to access. This set of nodes can be changed
> at any time via the cpuset interface and each individual memory policy is
> updated to reflect the changes for all attached tasks when this option is
> set.
More interactions between cpusets and memory policies. We have to be
careful here to keep clean semantics.
Isnt it a bit surprising for an application that has set up a custom
MPOL_INTERLEAVE policy if the nodes suddenly change because of a cpuset or
mems_allowed change?
-
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]
