Lines Matching refs: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
63 Note: When the feature of freeing unused vmemmap pages associated
64 with each hugetlb page is enabled, the number of surplus huge pages
66 pages when the system is under memory pressure.
71 pages of all sizes.
72 If huge pages of different sizes are in use, this number
82 pages in the kernel's huge page pool. "Persistent" huge pages will be
84 privileges can dynamically allocate more or free some persistent huge pages
87 Note: When the feature of freeing unused vmemmap pages associated with each
88 hugetlb page is enabled, we can fail to free the huge pages triggered by
91 Pages that are used as huge pages are reserved inside the kernel and cannot
92 be used for other purposes. Huge pages cannot be swapped out under
95 Once a number of huge pages have been pre-allocated to the kernel huge page
97 or shared memory system calls to use the huge pages. See the discussion of
100 The administrator can allocate persistent huge pages on the kernel boot
102 number of huge pages requested. This is the most reliable method of
103 allocating huge pages as memory has not yet become fragmented.
105 Some platforms support multiple huge page sizes. To allocate huge pages
106 of a specific size, one must precede the huge pages boot command parameters
115 parameter to preallocate a number of huge pages of the specified
125 Specify the number of huge pages to preallocate. This typically
128 implicitly specifies the number of huge pages of default size to
129 allocate. If the number of huge pages of default size is implicitly
132 node format. The node format specifies the number of huge pages
139 will result in 256 2M huge pages being allocated and a warning message
155 specific number of huge pages of default size. The number of default
156 sized huge pages to preallocate can also be implicitly specified as
164 will all result in 256 2M huge pages being allocated. Valid default
168 unused vmemmap pages associated with each HugeTLB page.
171 indicates the current number of pre-allocated huge pages of the default size.
173 default sized persistent huge pages::
177 This command will try to adjust the number of default sized huge pages in the
178 huge page pool to 20, allocating or freeing huge pages, as required.
185 silently skipped when allocating persistent huge pages. See the
188 with the allocation and freeing of persistent huge pages.
192 allocation attempt. If the kernel is unable to allocate huge pages from
194 allocating extra pages on other nodes with sufficient available contiguous
198 init files. This will enable the kernel to allocate huge pages early in
199 the boot process when the possibility of getting physical contiguous pages
200 is still very high. Administrators can verify the number of huge pages
202 distribution of huge pages in a NUMA system, use::
207 huge pages can grow, if more huge pages than ``/proc/sys/vm/nr_hugepages`` are
210 number of "surplus" huge pages from the kernel's normal page pool, when the
211 persistent huge page pool is exhausted. As these surplus huge pages become
215 surplus pages will first be promoted to persistent huge pages. Then, additional
216 huge pages will be allocated, if necessary and if possible, to fulfill
219 The administrator may shrink the pool of persistent huge pages for
221 smaller value. The kernel will attempt to balance the freeing of huge pages
223 Any free huge pages on the selected nodes will be freed back to the kernel's
227 it becomes less than the number of huge pages in use will convert the balance
228 of the in-use huge pages to surplus huge pages. This will occur even if
229 the number of surplus pages would exceed the overcommit value. As long as
231 increased sufficiently, or the surplus huge pages go out of use and are freed--
232 no more surplus huge pages will be allowed to be allocated.
249 pages may exist::
261 smaller huge pages. For example, the x86 architecture supports both
262 1GB and 2MB huge pages sizes. A 1GB huge page can be split into 512
263 2MB huge pages. Demote interfaces are not available for the smallest
267 is the size of demoted pages. When a page is demoted a corresponding
268 number of huge pages of demote_size will be created. By default,
272 pages size are allowed.
275 is used to demote a number of huge pages. A user with root privileges
277 requested number of huge pages. To determine how many pages were
289 Whether huge pages are allocated and freed via the ``/proc`` interface or
291 NUMA nodes from which huge pages are allocated or freed are controlled by the
296 The recommended method to allocate or free huge pages to/from the kernel
307 specified in <node-list>, depending on whether number of persistent huge pages
308 is initially less than or greater than 20, respectively. No huge pages will be
317 persistent huge pages will be distributed across the node or nodes
323 possibly, allocation of persistent huge pages on nodes not allowed by
346 subset of the system nodes to allocate huge pages outside the cpuset
350 of huge pages over all on-lines nodes with memory.
369 of free and surplus [overcommitted] huge pages, respectively, on the parent
372 The ``nr_hugepages`` attribute returns the total number of huge pages on the
374 pages on the parent node will be adjusted to the specified value, if sufficient
377 Note that the number of overcommit and reserve pages remain global quantities,
386 If the user applications are going to request huge pages using mmap system
395 ``/mnt/huge``. Any file created on ``/mnt/huge`` uses huge pages.
409 The ``size`` option sets the maximum value of memory (huge pages) allowed
414 The ``min_size`` option sets the minimum value of memory (huge pages) allowed
417 At mount time, the number of huge pages specified by ``min_size`` are reserved
419 If there are not enough free huge pages available, the mount will fail.
420 As huge pages are allocated to the filesystem and freed, the reserve count
421 is adjusted so that the sum of allocated and reserved huge pages is always
451 Syscalls that operate on memory backed by hugetlb pages only have their lengths
453 errno set to EINVAL or exclude hugetlb pages that extend beyond the length if