Lines Matching full:allowed

253 	MPOL_PREFERRED allowed for a mask rather than a single node.
259 	the user should not be remapped if the task or VMA's set of allowed
263         change in the set of allowed nodes, the preferred nodemask (Preferred
265         remapped to the new set of allowed nodes.  This may result in nodes
269 	nodes allowed by the task's cpuset, then the memory policy is
277 	3 is allowed from the user's nodemask, the "interleave" only
279 	now allowed, the Default behavior is used.
289 	set of allowed nodes.  The kernel stores the user-passed nodemask,
290 	and if the allowed nodes changes, then that original nodemask will
291 	be remapped relative to the new set of allowed nodes.
294 	mempolicy is rebound because of a change in the set of allowed
296 	remapped to the new set of allowed nodes.  That remap may not
298 	set of allowed nodes upon successive rebinds: a nodemask of
300 	allowed nodes is restored to its original state.
303 	the user's passed nodemask are relative to the set of allowed
307 	allowed nodes.  The nodemask passed by the user represents nodes
308 	relative to task or VMA's set of allowed nodes.
311 	of the new set of allowed nodes (for example, node 5 is set in
312 	the user's nodemask when the set of allowed nodes is only 0-3),
329 	set of memory nodes allowed by the task's cpuset, as that may
500 nodes whose memories are allowed by the cpuset constraints.  If the nodemask
501 specified for the policy contains nodes that are not allowed by the cpuset and
506 onto and folded into the task's set of allowed nodes as previously described.
512 memories are allowed in both cpusets may be used in the policies.  Obtaining
515 be attaching to the shared region.  Furthermore, if the cpusets' allowed