Lines Matching full:allowed

251 	MPOL_PREFERRED allowed for a mask rather than a single node.
257 	the user should not be remapped if the task or VMA's set of allowed
261         change in the set of allowed nodes, the preferred nodemask (Preferred
263         remapped to the new set of allowed nodes.  This may result in nodes
267 	nodes allowed by the task's cpuset, then the memory policy is
275 	3 is allowed from the user's nodemask, the "interleave" only
277 	now allowed, the Default behavior is used.
287 	set of allowed nodes.  The kernel stores the user-passed nodemask,
288 	and if the allowed nodes changes, then that original nodemask will
289 	be remapped relative to the new set of allowed nodes.
292 	mempolicy is rebound because of a change in the set of allowed
294 	remapped to the new set of allowed nodes.  That remap may not
296 	set of allowed nodes upon successive rebinds: a nodemask of
298 	allowed nodes is restored to its original state.
301 	the user's passed nodemask are relative to the set of allowed
305 	allowed nodes.  The nodemask passed by the user represents nodes
306 	relative to task or VMA's set of allowed nodes.
309 	of the new set of allowed nodes (for example, node 5 is set in
310 	the user's nodemask when the set of allowed nodes is only 0-3),
327 	set of memory nodes allowed by the task's cpuset, as that may
498 nodes whose memories are allowed by the cpuset constraints.  If the nodemask
499 specified for the policy contains nodes that are not allowed by the cpuset and
504 onto and folded into the task's set of allowed nodes as previously described.
510 memories are allowed in both cpusets may be used in the policies.  Obtaining
513 be attaching to the shared region.  Furthermore, if the cpusets' allowed