Lines Matching +full:mode +full:- +full:flag
10 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
16 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
19 programming interface that a NUMA-aware application can take advantage of. When
28 ------------------------
41 not to overload the initial boot node with boot-time
45 this is an optional, per-task policy. When defined for a
54 [clone() w/o the CLONE_VM flag] and exec*(). This allows a parent task
61 In a multi-threaded task, task policies apply only to the thread
93 mmap()ed with the MAP_ANONYMOUS flag. If a VMA policy is
95 used the MAP_SHARED flag. If the file mapping used the
96 MAP_PRIVATE flag, the VMA policy will only be applied when
98 mapping-- i.e., at Copy-On-Write.
101 virtual address space--a.k.a. threads--independent of when
106 are NOT inheritable across exec(). Thus, only NUMA-aware
109 * A task may install a new VMA policy on a sub-range of a
126 policies--using the mbind() system call specifying a range of
138 support allocation at fault time--a.k.a lazy allocation--so hugetlbfs
161 -----------------------------
163 A NUMA memory policy consists of a "mode", optional mode flags, and
164 an optional set of nodes. The mode determines the behavior of the
165 policy, the optional mode flags determine the behavior of the mode,
175 Default Mode--MPOL_DEFAULT
176 This mode is only used in the memory policy APIs. Internally,
178 policy scopes. Any existing non-default policy will simply be
187 When specified in one of the memory policy APIs, the Default mode
191 be non-empty.
194 This mode specifies that memory must come from the set of
200 This mode specifies that the allocation should be attempted
206 Internally, the Preferred policy uses a single node--the
208 mode flag MPOL_F_LOCAL is set, the preferred_node is ignored
216 mode. If an empty nodemask is passed, the policy cannot use
221 This mode specifies that page allocations be interleaved, on a
223 This mode also behaves slightly differently, based on the
227 Interleave mode indexes the set of nodes specified by the
236 For allocation of page cache pages, Interleave mode indexes
244 interleaved system default policy works in this mode.
247 This mode specifies that the allocation should be preferably
254 This mode operates the same as MPOL_INTERLEAVE, except that
262 NUMA memory policy supports the following optional mode flags:
265 This flag specifies that the nodemask passed by
269 Without this flag, any time a mempolicy is rebound because of a
275 With this flag, if the user-specified nodes overlap with the
281 mems 1-3 that sets an Interleave policy over the same set. If
282 the cpuset's mems change to 3-5, the Interleave will now occur
283 over nodes 3, 4, and 5. With this flag, however, since only node
289 MPOL_F_RELATIVE_NODES flag. It also cannot be used for
294 This flag specifies that the nodemask passed
296 set of allowed nodes. The kernel stores the user-passed nodemask,
300 Without this flag (and without MPOL_F_STATIC_NODES), anytime a
306 1,3,5 may be remapped to 7-9 and then to 1-3 if the set of
309 With this flag, the remap is done so that the node numbers from
319 the user's nodemask when the set of allowed nodes is only 0-3),
324 mems 2-5 that sets an Interleave policy over the same set with
325 MPOL_F_RELATIVE_NODES. If the cpuset's mems change to 3-7, the
326 interleave now occurs over nodes 3,5-7. If the cpuset's mems
327 then change to 0,2-3,5, then the interleave occurs over nodes
328 0,2-3,5.
331 nodemasks to specify memory policies using this flag should
334 memory nodes 0 to N-1, where N is the number of memory nodes the
340 MPOL_F_STATIC_NODES flag. It also cannot be used for
359 During run-time "usage" of the policy, we attempt to minimize atomic operations
367 2) examination of the policy to determine the policy mode and associated node
400 used for non-shared policies. For this reason, shared policies are marked
401 as such, and the extra reference is dropped "conditionally"--i.e., only
426 prefix, are defined in <linux/syscalls.h>; the mode and flag
431 long set_mempolicy(int mode, const unsigned long *nmask,
434 Set's the calling task's "task/process memory policy" to mode
435 specified by the 'mode' argument and the set of nodes defined by
437 'maxnode' ids. Optional mode flags may be passed by combining the
438 'mode' argument with the flag (for example: MPOL_INTERLEAVE |
446 long get_mempolicy(int *mode,
459 long mbind(void *start, unsigned long len, int mode,
463 mbind() installs the policy specified by (mode, nmask, maxnodes) as a
495 The numactl(8) tool is packaged with the run-time version of the library
497 package the headers and compile-time libraries in a separate development