Lines Matching refs:with

16 First the Linux kernel needs to be built with the CONFIG_HUGETLBFS
56 returned to the huge page pool when freed by a task.  A user with root
65 pool, a user with appropriate privilege can use either the mmap system call
76 with a huge page size selection parameter "hugepagesz=<size>".  <size> must
77 be specified in bytes with optional scale suffix [kKmMgG].  The default huge
78 page size may be selected with the "default_hugepagesz=<size>" boot parameter.
93 task has default memory policy--is all on-line nodes with memory.  Allowed
94 nodes with insufficient available, contiguous memory for a huge page will be
97 with the allocation and freeing of persistent huge pages.
103 allocating extra pages on other nodes with sufficient available contiguous
167 Interaction of Task Memory Policy with Huge Page Allocation/Freeing
201    neighbor node with sufficient contiguous memory.  To do this would cause
206 2) One or more nodes may be specified with the bind or interleave policy.
207    If more than one node is specified with the preferred policy, only the
219    shell with non-default policy, that policy will be used.  One can specify a
220    node list of "all" with numactl --interleave or --membind [-m] to achieve
225    be no way for a task with non-default policy running in a cpuset with a
230    of huge pages over all on-lines nodes with memory.
237 NUMA node with memory in:
302 Regular chown, chgrp, and chmod commands (with right permissions) could be
306 applications are going to use only shmat/shmget system calls or mmap with
307 MAP_HUGETLB.  For an example of how to use mmap with MAP_HUGETLB see map_hugetlb
317 aligned to the native page size of the processor; they will normally fail with
333    wide range of userspace tools to help with huge page usability, environment