Lines Matching refs:nodes
13 which is an administrative mechanism for restricting the nodes from which
31 default policy will be set to interleave allocations across all nodes
140 optional set of nodes. The mode determines the behavior of the policy,
142 optional set of nodes can be viewed as the arguments to the policy
162 does not use the optional set of nodes.
164 It is an error for the set of nodes specified for this policy to
168 set of nodes specified by the policy. Memory will be allocated from
174 allocation fails, the kernel will search other nodes, in order of
192 interleaved, on a page granularity, across the nodes specified in
197 Interleave mode indexes the set of nodes specified by the policy
199 [VMA] containing the address modulo the number of nodes specified
206 of nodes specified by the policy using a node counter maintained
209 spread the pages out over the nodes specified by the policy based
219 nodes changes after the memory policy has been defined.
222 change in the set of allowed nodes, the node (Preferred) or
224 allowed nodes. This may result in nodes being used that were
227 With this flag, if the user-specified nodes overlap with the
228 nodes allowed by the task's cpuset, then the memory policy is
229 applied to their intersection. If the two sets of nodes do not
235 over nodes 3, 4, and 5. With this flag, however, since only node
237 occurs over that node. If no nodes from the user's nodemask are
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.
253 nodes, the node (Preferred) or nodemask (Bind, Interleave) is
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.
262 nodes. In other words, if nodes 0, 2, and 4 are set in the user's
264 Bind or Interleave case, the third and fifth) nodes in the set of
265 allowed nodes. The nodemask passed by the user represents nodes
266 relative to task or VMA's set of allowed nodes.
268 If the user's nodemask includes nodes that are outside the range
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),
277 interleave now occurs over nodes 3,5-7. If the cpuset's mems
278 then change to 0,2-3,5, then the interleave occurs over nodes
285 memory nodes 0 to N-1, where N is the number of memory nodes the
287 set of memory nodes allowed by the task's cpuset, as that may
311 and NUMA nodes. "Usage" here means one of the following:
321 BIND policy nodemask is used, by reference, to filter ineligible nodes.
358 on different NUMA nodes. This extra overhead can be avoided by always
381 specified by the 'mode' argument and the set of nodes defined
435 that require a node or set of nodes, the nodes are restricted to the set of
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
438 MPOL_F_RELATIVE_NODES is not used, the intersection of the set of nodes
439 specified for the policy and the set of nodes with memory is used. If the
441 installed. If MPOL_F_RELATIVE_NODES is used, the policy's nodes are mapped
442 onto and folded into the task's set of allowed nodes as previously described.
447 any of the tasks install shared policy on the region, only nodes whose