Lines Matching +full:kernel +full:- +full:policy
9 the Linux kernel. This support is built on top of multiple page size support
13 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
19 Users can use the huge page support in Linux kernel by either using the mmap
22 First the Linux kernel needs to be built with the CONFIG_HUGETLBFS
28 persistent hugetlb pages in the kernel's huge page pool. It also displays
73 ``/sys/kernel/mm/hugepages`` (described below).
77 configured in the kernel.
80 pages in the kernel's huge page pool. "Persistent" huge pages will be
89 Pages that are used as huge pages are reserved inside the kernel and cannot
93 Once a number of huge pages have been pre-allocated to the kernel huge page
98 The administrator can allocate persistent huge pages on the kernel boot
169 indicates the current number of pre-allocated huge pages of the default size.
178 On a NUMA platform, the kernel will attempt to distribute the huge page pool
179 over all the set of allowed nodes specified by the NUMA memory policy of the
180 task that modifies ``nr_hugepages``. The default for the allowed nodes--when the
181 task has default memory policy--is all on-line nodes with memory. Allowed
185 of the interaction of task memory policy, cpusets and per node attributes
190 allocation attempt. If the kernel is unable to allocate huge pages from
196 init files. This will enable the kernel to allocate huge pages early in
206 requested by applications. Writing any non-zero value into this file
208 number of "surplus" huge pages from the kernel's normal page pool, when the
210 unused, they are freed back to the kernel's normal page pool.
219 smaller value. The kernel will attempt to balance the freeing of huge pages
220 across all nodes in the memory policy of the task modifying ``nr_hugepages``.
221 Any free huge pages on the selected nodes will be freed back to the kernel's
226 of the in-use huge pages to surplus huge pages. This will occur even if
228 this condition holds--that is, until ``nr_hugepages+nr_overcommit_hugepages`` is
229 increased sufficiently, or the surplus huge pages go out of use and are freed--
232 With support for multiple huge page pools at run-time available, much of
238 /sys/kernel/mm/hugepages
240 For each huge page size supported by the running kernel, a subdirectory
243 hugepages-${size}kB
280 demote_size) function as described above for the default huge page-sized case.
284 Interaction of Task Memory Policy with Huge Page Allocation/Freeing
290 NUMA memory policy of the task that modifies the ``nr_hugepages_mempolicy``
294 The recommended method to allocate or free huge pages to/from the kernel
297 numactl --interleave <node-list> echo 20 \
302 numactl -m <node-list> echo 20 >/proc/sys/vm/nr_hugepages_mempolicy
304 This will allocate or free ``abs(20 - nr_hugepages)`` to or from the nodes
305 specified in <node-list>, depending on whether number of persistent huge pages
307 allocated nor freed on any node not included in the specified <node-list>.
310 memory policy mode--bind, preferred, local or interleave--may be used. The
314 Documentation/admin-guide/mm/numa_memory_policy.rst],
317 However, if a node in the policy does not contain sufficient contiguous
322 the task's memory policy.
324 #. One or more nodes may be specified with the bind or interleave policy.
325 If more than one node is specified with the preferred policy, only the
326 lowest numeric id will be used. Local policy will select the node where
328 For local policy to be deterministic, the task must be bound to a cpu or
331 indeterminate. Thus, local policy is not very useful for this purpose.
334 #. The nodes allowed mask will be derived from any non-default task mempolicy,
335 whether this policy was set explicitly by the task itself or one of its
337 shell with non-default policy, that policy will be used. One can specify a
338 node list of "all" with numactl --interleave or --membind [-m] to achieve
341 #. Any task mempolicy specified--e.g., using numactl--will be constrained by
343 be no way for a task with non-default policy running in a cpuset with a
347 #. Boot-time huge page allocation attempts to distribute the requested number
348 of huge pages over all on-lines nodes with memory.
357 /sys/devices/system/node/node[0-9]*/hugepages/
366 The free\_' and surplus\_' attribute files are read-only. They return the number
379 The hugetlb may be migrated between the per-node hugepages pool in the following
384 hugetlb migration, that means these 3 cases can break the per-node hugepages pool.
395 mount -t hugetlbfs \
396 -o uid=<value>,gid=<value>,mode=<value>,pagesize=<value>,size=<value>,\
471 ``hugepage-shm``
472 see tools/testing/selftests/mm/hugepage-shm.c
474 ``hugepage-mmap``
475 see tools/testing/selftests/mm/hugepage-mmap.c