Lines Matching refs:nodes
19 which is an administrative mechanism for restricting the nodes from which
42 allocations across all nodes with "sufficient" memory, so as
166 an optional set of nodes. The mode determines the behavior of the
168 and the optional set of nodes can be viewed as the arguments to the
190 does not use the optional set of nodes.
192 It is an error for the set of nodes specified for this policy to
197 nodes specified by the policy. Memory will be allocated from
204 allocation fails, the kernel will search other nodes, in order
224 page granularity, across the nodes specified in the policy.
229 Interleave mode indexes the set of nodes specified by the
232 nodes specified by the policy. It then attempts to allocate a
239 the set of nodes specified by the policy using a node counter
242 This will tend to spread the pages out over the nodes
251 a memory pressure on all nodes in the nodemask, the allocation
252 can fall back to all existing numa nodes. This is effectively
260 nodes changes after the memory policy has been defined.
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
268 With this flag, if the user-specified nodes overlap with the
269 nodes allowed by the task's cpuset, then the memory policy is
270 applied to their intersection. If the two sets of nodes do not
276 over nodes 3, 4, and 5. With this flag, however, since only node
278 occurs over that node. If no nodes from the user's nodemask are
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.
295 nodes, the node (Preferred) or nodemask (Bind, Interleave) is
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.
304 nodes. In other words, if nodes 0, 2, and 4 are set in the user's
306 Bind or Interleave case, the third and fifth) nodes in the set of
307 allowed nodes. The nodemask passed by the user represents nodes
308 relative to task or VMA's set of allowed nodes.
310 If the user's nodemask includes nodes that are outside the range
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),
319 interleave now occurs over nodes 3,5-7. If the cpuset's mems
320 then change to 0,2-3,5, then the interleave occurs over nodes
327 memory nodes 0 to N-1, where N is the number of memory nodes the
329 set of memory nodes allowed by the task's cpuset, as that may
354 and NUMA nodes. "Usage" here means one of the following:
364 BIND policy nodemask is used, by reference, to filter ineligible nodes.
401 on different NUMA nodes. This extra overhead can be avoided by always
428 specified by the 'mode' argument and the set of nodes defined by
485 that require a node or set of nodes, the nodes are restricted to the set of
486 nodes whose memories are allowed by the cpuset constraints. If the nodemask
487 specified for the policy contains nodes that are not allowed by the cpuset and
488 MPOL_F_RELATIVE_NODES is not used, the intersection of the set of nodes
489 specified for the policy and the set of nodes with memory is used. If the
491 installed. If MPOL_F_RELATIVE_NODES is used, the policy's nodes are mapped
492 onto and folded into the task's set of allowed nodes as previously described.
497 any of the tasks install shared policy on the region, only nodes whose