Lines Matching full:allowed

251 	MPOL_PREFERRED allowed for a mask rather than a single node.
266 	the user should not be remapped if the task or VMA's set of allowed
270         change in the set of allowed nodes, the preferred nodemask (Preferred
272         remapped to the new set of allowed nodes.  This may result in nodes
276 	nodes allowed by the task's cpuset, then the memory policy is
284 	3 is allowed from the user's nodemask, the "interleave" only
286 	now allowed, the Default behavior is used.
296 	set of allowed nodes.  The kernel stores the user-passed nodemask,
297 	and if the allowed nodes changes, then that original nodemask will
298 	be remapped relative to the new set of allowed nodes.
301 	mempolicy is rebound because of a change in the set of allowed
303 	remapped to the new set of allowed nodes.  That remap may not
305 	set of allowed nodes upon successive rebinds: a nodemask of
307 	allowed nodes is restored to its original state.
310 	the user's passed nodemask are relative to the set of allowed
314 	allowed nodes.  The nodemask passed by the user represents nodes
315 	relative to task or VMA's set of allowed nodes.
318 	of the new set of allowed nodes (for example, node 5 is set in
319 	the user's nodemask when the set of allowed nodes is only 0-3),
336 	set of memory nodes allowed by the task's cpuset, as that may
507 nodes whose memories are allowed by the cpuset constraints.  If the nodemask
508 specified for the policy contains nodes that are not allowed by the cpuset and
513 onto and folded into the task's set of allowed nodes as previously described.
519 memories are allowed in both cpusets may be used in the policies.  Obtaining
522 be attaching to the shared region.  Furthermore, if the cpusets' allowed