Lines Matching +full:page +full:- +full:based
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 ------------------------
35 that governs all page allocations that aren't controlled by
41 not to overload the initial boot node with boot-time
45 this is an optional, per-task policy. When defined for a
46 specific task, this policy controls all page allocations made
49 all page allocations that would have been controlled by the
61 In a multi-threaded task, task policies apply only to the thread
69 changes its task policy remain where they were allocated based on
97 an anonymous page is allocated on an attempt to write to the
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
116 VMA range remain where they were allocated based on the
118 2.6.16, Linux supports page migration via the mbind() system
119 call, so that page contents can be moved to match a newly
126 policies--using the mbind() system call specifying a range of
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.
203 of increasing distance from the preferred node based on
206 Internally, the Preferred policy uses a single node--the
221 This mode specifies that page allocations be interleaved, on a
222 page granularity, across the nodes specified in the policy.
223 This mode also behaves slightly differently, based on the
228 policy using the page offset of the faulting address into the
231 page, starting at the selected node, as if the node had been
236 For allocation of page cache pages, Interleave mode indexes
241 specified by the policy based on the order in which they are
242 allocated, rather than based on any page offset into an
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
359 or node lists, if any, for page allocation. This is considered a "hot
361 allocation process, which may sleep during page reclamation, because the
378 3) Page allocation usage of task or vma policy occurs in the fault path where
381 freed out from under us while we're using it for page allocation.
385 querying or allocating a page based on the policy. To resolve this
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
397 more expensive to use in the page allocation path. This is especially
432 See the set_mempolicy(2) man page for more details
445 See the get_mempolicy(2) man page for more details
459 See the mbind(2) man page for more details.
470 closest to which page allocation will come from. Specifying the home node override
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