admin-guide/mm/numa_memory_policy.rst

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
61 	In a multi-threaded task, task policies apply only to the thread
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 -----------------------------
166 and the optional set of nodes can be viewed as the arguments to the
175 Default Mode--MPOL_DEFAULT
178 	policy scopes.  Any existing non-default policy will simply be
191 	be non-empty.
206 	Internally, the Preferred policy uses a single node--the
210 	allocation policy can be viewed as a Preferred policy that
211 	starts at the node containing the cpu where the allocation
266 	With this flag, if the user-specified nodes overlap with the
272 	mems 1-3 that sets an Interleave policy over the same set.  If
273 	the cpuset's mems change to 3-5, the Interleave will now occur
287 	set of allowed nodes.  The kernel stores the user-passed nodemask,
297 	1,3,5 may be remapped to 7-9 and then to 1-3 if the set of
310 	the user's nodemask when the set of allowed nodes is only 0-3),
315 	mems 2-5 that sets an Interleave policy over the same set with
316 	MPOL_F_RELATIVE_NODES.  If the cpuset's mems change to 3-7, the
317 	interleave now occurs over nodes 3,5-7.  If the cpuset's mems
318 	then change to 0,2-3,5, then the interleave occurs over nodes
319 	0,2-3,5.
325 	memory nodes 0 to N-1, where N is the number of memory nodes the
350 During run-time "usage" of the policy, we attempt to minimize atomic operations
391    used for non-shared policies.  For this reason, shared policies are marked
392    as such, and the extra reference is dropped "conditionally"--i.e., only
472 executing CPU.
486 The numactl(8) tool is packaged with the run-time version of the library
488 package the headers and compile-time libraries in a separate development