Lines Matching full:pages
4 HugeTLB Pages
30 persistent hugetlb pages in the kernel's huge page pool. It also displays
32 and surplus huge pages in the pool of huge pages of default size.
48 is the size of the pool of huge pages.
50 is the number of huge pages in the pool that are not yet
53 is short for "reserved," and is the number of huge pages for
55 but no allocation has yet been made. Reserved huge pages
57 huge page from the pool of huge pages at fault time.
59 is short for "surplus," and is the number of huge pages in
61 maximum number of surplus huge pages is controlled by
67 pages of all sizes.
68 If huge pages of different sizes are in use, this number
78 pages in the kernel's huge page pool. "Persistent" huge pages will be
80 privileges can dynamically allocate more or free some persistent huge pages
83 Pages that are used as huge pages are reserved inside the kernel and cannot
84 be used for other purposes. Huge pages cannot be swapped out under
87 Once a number of huge pages have been pre-allocated to the kernel huge page
89 or shared memory system calls to use the huge pages. See the discussion of
90 :ref:`Using Huge Pages <using_huge_pages>`, below.
92 The administrator can allocate persistent huge pages on the kernel boot
94 number of huge pages requested. This is the most reliable method of
95 allocating huge pages as memory has not yet become fragmented.
97 Some platforms support multiple huge page sizes. To allocate huge pages
98 of a specific size, one must precede the huge pages boot command parameters
107 parameter to preallocate a number of huge pages of the specified
117 Specify the number of huge pages to preallocate. This typically
120 implicitly specifies the number of huge pages of default size to
121 allocate. If the number of huge pages of default size is implicitly
129 will result in 256 2M huge pages being allocated and a warning message
137 specific number of huge pages of default size. The number of default
138 sized huge pages to preallocate can also be implicitly specified as
146 will all result in 256 2M huge pages being allocated. Valid default
150 indicates the current number of pre-allocated huge pages of the default size.
152 default sized persistent huge pages::
156 This command will try to adjust the number of default sized huge pages in the
157 huge page pool to 20, allocating or freeing huge pages, as required.
164 silently skipped when allocating persistent huge pages. See the
167 with the allocation and freeing of persistent huge pages.
171 allocation attempt. If the kernel is unable to allocate huge pages from
173 allocating extra pages on other nodes with sufficient available contiguous
177 init files. This will enable the kernel to allocate huge pages early in
178 the boot process when the possibility of getting physical contiguous pages
179 is still very high. Administrators can verify the number of huge pages
181 distribution of huge pages in a NUMA system, use::
186 huge pages can grow, if more huge pages than ``/proc/sys/vm/nr_hugepages`` are
189 number of "surplus" huge pages from the kernel's normal page pool, when the
190 persistent huge page pool is exhausted. As these surplus huge pages become
194 surplus pages will first be promoted to persistent huge pages. Then, additional
195 huge pages will be allocated, if necessary and if possible, to fulfill
198 The administrator may shrink the pool of persistent huge pages for
200 smaller value. The kernel will attempt to balance the freeing of huge pages
202 Any free huge pages on the selected nodes will be freed back to the kernel's
206 it becomes less than the number of huge pages in use will convert the balance
207 of the in-use huge pages to surplus huge pages. This will occur even if
208 the number of surplus pages would exceed the overcommit value. As long as
210 increased sufficiently, or the surplus huge pages go out of use and are freed--
211 no more surplus huge pages will be allowed to be allocated.
242 Whether huge pages are allocated and freed via the ``/proc`` interface or
244 NUMA nodes from which huge pages are allocated or freed are controlled by the
249 The recommended method to allocate or free huge pages to/from the kernel
260 specified in <node-list>, depending on whether number of persistent huge pages
261 is initially less than or greater than 20, respectively. No huge pages will be
270 persistent huge pages will be distributed across the node or nodes
276 possibly, allocation of persistent huge pages on nodes not allowed by
299 subset of the system nodes to allocate huge pages outside the cpuset
303 of huge pages over all on-lines nodes with memory.
322 of free and surplus [overcommitted] huge pages, respectively, on the parent
325 The ``nr_hugepages`` attribute returns the total number of huge pages on the
327 pages on the parent node will be adjusted to the specified value, if sufficient
330 Note that the number of overcommit and reserve pages remain global quantities,
336 Using Huge Pages
339 If the user applications are going to request huge pages using mmap system
348 ``/mnt/huge``. Any file created on ``/mnt/huge`` uses huge pages.
362 The ``size`` option sets the maximum value of memory (huge pages) allowed
367 The ``min_size`` option sets the minimum value of memory (huge pages) allowed
370 At mount time, the number of huge pages specified by ``min_size`` are reserved
372 If there are not enough free huge pages available, the mount will fail.
373 As huge pages are allocated to the filesystem and freed, the reserve count
374 is adjusted so that the sum of allocated and reserved huge pages is always
404 Syscalls that operate on memory backed by hugetlb pages only have their lengths
406 errno set to EINVAL or exclude hugetlb pages that extend beyond the length if