Lines Matching +full:parameter +full:- +full:less
15 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
95 Once a number of huge pages have been pre-allocated to the kernel huge page
101 command line by specifying the "hugepages=N" parameter, where 'N' = the
107 with a huge page size selection parameter "hugepagesz=<size>". <size> must
109 page size may be selected with the "default_hugepagesz=<size>" boot parameter.
111 Hugetlb boot command line parameter semantics
115 parameter to preallocate a number of huge pages of the specified
126 follows a valid hugepagesz or default_hugepagesz parameter. However,
127 if hugepages is the first or only hugetlb command line parameter it
131 parameter pair for the default size.
138 indicating that the hugepages=512 parameter is ignored. If a hugepages
139 parameter is preceded by an invalid hugepagesz parameter, it will
142 Specify the default huge page size. This parameter can
144 optionally be followed by the hugepages parameter to preallocate a
161 indicates the current number of pre-allocated huge pages of the default size.
172 task that modifies ``nr_hugepages``. The default for the allowed nodes--when the
173 task has default memory policy--is all on-line nodes with memory. Allowed
198 requested by applications. Writing any non-zero value into this file
217 it becomes less than the number of huge pages in use will convert the balance
218 of the in-use huge pages to surplus huge pages. This will occur even if
220 this condition holds--that is, until ``nr_hugepages+nr_overcommit_hugepages`` is
221 increased sufficiently, or the surplus huge pages go out of use and are freed--
224 With support for multiple huge page pools at run-time available, much of
235 hugepages-${size}kB
246 which function as described above for the default huge page-sized case.
263 numactl --interleave <node-list> echo 20 \
268 numactl -m <node-list> echo 20 >/proc/sys/vm/nr_hugepages_mempolicy
270 This will allocate or free ``abs(20 - nr_hugepages)`` to or from the nodes
271 specified in <node-list>, depending on whether number of persistent huge pages
272 is initially less than or greater than 20, respectively. No huge pages will be
273 allocated nor freed on any node not included in the specified <node-list>.
276 memory policy mode--bind, preferred, local or interleave--may be used. The
280 :ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`],
300 #. The nodes allowed mask will be derived from any non-default task mempolicy,
303 shell with non-default policy, that policy will be used. One can specify a
304 node list of "all" with numactl --interleave or --membind [-m] to achieve
307 #. Any task mempolicy specified--e.g., using numactl--will be constrained by
309 be no way for a task with non-default policy running in a cpuset with a
313 #. Boot-time huge page allocation attempts to distribute the requested number
314 of huge pages over all on-lines nodes with memory.
323 /sys/devices/system/node/node[0-9]*/hugepages/
332 The free\_' and surplus\_' attribute files are read-only. They return the number
354 mount -t hugetlbfs \
355 -o uid=<value>,gid=<value>,mode=<value>,pagesize=<value>,size=<value>,\
430 ``hugepage-shm``
431 see tools/testing/selftests/vm/hugepage-shm.c
433 ``hugepage-mmap``
434 see tools/testing/selftests/vm/hugepage-mmap.c