Lines Matching +full:boot +full:- +full:pages
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 ------------------------
38 use "local allocation" described below. However, during boot
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
67 A task policy applies only to pages allocated after the policy is
68 installed. Any pages already faulted in by the task when the task
82 A VMA policy will govern the allocation of pages that back
90 * VMA policy applies ONLY to anonymous pages. These include
91 pages allocated for anonymous segments, such as the task
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
114 * By default, VMA policy applies only to pages allocated after
115 the policy is installed. Any pages already faulted into the
126 policies--using the mbind() system call specifying a range of
131 the object share the policy, and all pages allocated for the
138 support allocation at fault time--a.k.a lazy allocation--so hugetlbfs
144 allocations of page cache pages for regular files mmap()ed
147 shared page cache pages, including pages backing private
161 -----------------------------
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
226 For allocation of anonymous pages and shared memory pages,
236 For allocation of page cache pages, Interleave mode indexes
240 This will tend to spread the pages out over the nodes
243 address range or file. During system boot up, the temporary
258 Weighted interleave allocates pages on nodes according to a
259 weight. For example if nodes [0,1] are weighted [5,2], 5 pages
260 will be allocated on node0 for every 2 pages allocated on node1.
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
296 set of allowed nodes. The kernel stores the user-passed nodemask,
306 1,3,5 may be remapped to 7-9 and then to 1-3 if the set of
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.
334 memory nodes 0 to N-1, where N is the number of memory nodes the
359 During run-time "usage" of the policy, we attempt to minimize atomic operations
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
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