Lines Matching +full:non +full:- +full:specified
15 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
87 Once a number of huge pages have been pre-allocated to the kernel huge page
100 be specified in bytes with optional scale suffix [kKmMgG]. The default huge
107 parameter to preallocate a number of huge pages of the specified
108 size. Hence, hugepagesz and hugepages are typically specified in
113 hugepagesz can only be specified once on the command line for a
122 specified, it can not be overwritten by a hugepagesz,hugepages
135 only be specified once on the command line. default_hugepagesz can
138 sized huge pages to preallocate can also be implicitly specified as
150 indicates the current number of pre-allocated huge pages of the default size.
160 over all the set of allowed nodes specified by the NUMA memory policy of the
161 task that modifies ``nr_hugepages``. The default for the allowed nodes--when the
162 task has default memory policy--is all on-line nodes with memory. Allowed
187 requested by applications. Writing any non-zero value into this file
207 of the in-use huge pages to surplus huge pages. This will occur even if
209 this condition holds--that is, until ``nr_hugepages+nr_overcommit_hugepages`` is
210 increased sufficiently, or the surplus huge pages go out of use and are freed--
213 With support for multiple huge page pools at run-time available, much of
224 hugepages-${size}kB
235 which function as described above for the default huge page-sized case.
252 numactl --interleave <node-list> echo 20 \
257 numactl -m <node-list> echo 20 >/proc/sys/vm/nr_hugepages_mempolicy
259 This will allocate or free ``abs(20 - nr_hugepages)`` to or from the nodes
260 specified in <node-list>, depending on whether number of persistent huge pages
262 allocated nor freed on any node not included in the specified <node-list>.
265 memory policy mode--bind, preferred, local or interleave--may be used. The
269 :ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`],
271 specified in the mempolicy as if "interleave" had been specified.
279 #. One or more nodes may be specified with the bind or interleave policy.
280 If more than one node is specified with the preferred policy, only the
289 #. The nodes allowed mask will be derived from any non-default task mempolicy,
292 shell with non-default policy, that policy will be used. One can specify a
293 node list of "all" with numactl --interleave or --membind [-m] to achieve
296 #. Any task mempolicy specified--e.g., using numactl--will be constrained by
298 be no way for a task with non-default policy running in a cpuset with a
302 #. Boot-time huge page allocation attempts to distribute the requested number
303 of huge pages over all on-lines nodes with memory.
312 /sys/devices/system/node/node[0-9]*/hugepages/
321 The free\_' and surplus\_' attribute files are read-only. They return the number
326 specified node. When this attribute is written, the number of persistent huge
327 pages on the parent node will be adjusted to the specified value, if sufficient
343 mount -t hugetlbfs \
344 -o uid=<value>,gid=<value>,mode=<value>,pagesize=<value>,size=<value>,\
359 is specified in bytes. If ``pagesize`` is not specified the platform's
363 for that filesystem (``/mnt/huge``). The ``size`` option can be specified
364 in bytes, or as a percentage of the specified huge page pool (``nr_hugepages``).
368 for the filesystem. ``min_size`` can be specified in the same way as ``size``,
370 At mount time, the number of huge pages specified by ``min_size`` are reserved
419 ``hugepage-shm``
420 see tools/testing/selftests/vm/hugepage-shm.c
422 ``hugepage-mmap``
423 see tools/testing/selftests/vm/hugepage-mmap.c