Lines Matching full:allowed

252 	the user should not be remapped if the task or VMA's set of allowed
256 	change in the set of allowed nodes, the node (Preferred) or
258 	allowed nodes.  This may result in nodes being used that were
262 	nodes allowed by the task's cpuset, then the memory policy is
270 	3 is allowed from the user's nodemask, the "interleave" only
272 	now allowed, the Default behavior is used.
282 	set of allowed nodes.  The kernel stores the user-passed nodemask,
283 	and if the allowed nodes changes, then that original nodemask will
284 	be remapped relative to the new set of allowed nodes.
287 	mempolicy is rebound because of a change in the set of allowed
289 	remapped to the new set of allowed nodes.  That remap may not
291 	set of allowed nodes upon successive rebinds: a nodemask of
293 	allowed nodes is restored to its original state.
296 	the user's passed nodemask are relative to the set of allowed
300 	allowed nodes.  The nodemask passed by the user represents nodes
301 	relative to task or VMA's set of allowed nodes.
304 	of the new set of allowed nodes (for example, node 5 is set in
305 	the user's nodemask when the set of allowed nodes is only 0-3),
322 	set of memory nodes allowed by the task's cpuset, as that may
479 nodes whose memories are allowed by the cpuset constraints.  If the nodemask
480 specified for the policy contains nodes that are not allowed by the cpuset and
485 onto and folded into the task's set of allowed nodes as previously described.
491 memories are allowed in both cpusets may be used in the policies.  Obtaining
494 be attaching to the shared region.  Furthermore, if the cpusets' allowed