Lines Matching refs:allowed

218 	the user should not be remapped if the task or VMA's set of allowed
222 	    change in the set of allowed nodes, the node (Preferred) or
224 	    allowed nodes.  This may result in nodes being used that were
228 	    nodes allowed by the task's cpuset, then the memory policy is
236 	    3 is allowed from the user's nodemask, the "interleave" only
238 	    now allowed, the Default behavior is used.
247 	set of allowed nodes.  The kernel stores the user-passed nodemask,
248 	and if the allowed nodes changes, then that original nodemask will
249 	be remapped relative to the new set of allowed nodes.
252 	    mempolicy is rebound because of a change in the set of allowed
254 	    remapped to the new set of allowed nodes.  That remap may not
256 	    set of allowed nodes upon successive rebinds: a nodemask of
258 	    allowed nodes is restored to its original state.
261 	    the user's passed nodemask are relative to the set of allowed
265 	    allowed nodes.  The nodemask passed by the user represents nodes
266 	    relative to task or VMA's set of allowed nodes.
269 	    of the new set of allowed nodes (for example, node 5 is set in
270 	    the user's nodemask when the set of allowed nodes is only 0-3),
287 	    set of memory nodes allowed by the task's cpuset, as that may
436 nodes whose memories are allowed by the cpuset constraints.  If the nodemask
437 specified for the policy contains nodes that are not allowed by the cpuset and
442 onto and folded into the task's set of allowed nodes as previously described.
448 memories are allowed in both cpusets may be used in the policies.  Obtaining
451 be attaching to the shared region.  Furthermore, if the cpusets' allowed