Lines Matching refs:pages
22 persistent hugetlb pages in the kernel's huge page pool. It also displays
23 information about the number of free, reserved and surplus huge pages and the
38 HugePages_Total is the size of the pool of huge pages.
39 HugePages_Free is the number of huge pages in the pool that are not yet
41 HugePages_Rsvd is short for "reserved," and is the number of huge pages for
43 but no allocation has yet been made. Reserved huge pages
45 huge page from the pool of huge pages at fault time.
46 HugePages_Surp is short for "surplus," and is the number of huge pages in
48 maximum number of surplus huge pages is controlled by
55 pages in the kernel's huge page pool. "Persistent" huge pages will be
57 privileges can dynamically allocate more or free some persistent huge pages
60 Pages that are used as huge pages are reserved inside the kernel and cannot
61 be used for other purposes. Huge pages cannot be swapped out under
64 Once a number of huge pages have been pre-allocated to the kernel huge page
66 or shared memory system calls to use the huge pages. See the discussion of
69 The administrator can allocate persistent huge pages on the kernel boot
71 number of huge pages requested. This is the most reliable method of
72 allocating huge pages as memory has not yet become fragmented.
74 Some platforms support multiple huge page sizes. To allocate huge pages
75 of a specific size, one must precede the huge pages boot command parameters
81 indicates the current number of pre-allocated huge pages of the default size.
83 default sized persistent huge pages:
87 This command will try to adjust the number of default sized huge pages in the
88 huge page pool to 20, allocating or freeing huge pages, as required.
95 silently skipped when allocating persistent huge pages. See the discussion
97 with the allocation and freeing of persistent huge pages.
101 allocation attempt. If the kernel is unable to allocate huge pages from
103 allocating extra pages on other nodes with sufficient available contiguous
107 init files. This will enable the kernel to allocate huge pages early in
108 the boot process when the possibility of getting physical contiguous pages
109 is still very high. Administrators can verify the number of huge pages
111 distribution of huge pages in a NUMA system, use:
116 huge pages can grow, if more huge pages than /proc/sys/vm/nr_hugepages are
119 number of "surplus" huge pages from the kernel's normal page pool, when the
120 persistent huge page pool is exhausted. As these surplus huge pages become
124 pages will first be promoted to persistent huge pages. Then, additional
125 huge pages will be allocated, if necessary and if possible, to fulfill
128 The administrator may shrink the pool of persistent huge pages for
130 smaller value. The kernel will attempt to balance the freeing of huge pages
132 Any free huge pages on the selected nodes will be freed back to the kernel's
136 it becomes less than the number of huge pages in use will convert the balance
137 of the in-use huge pages to surplus huge pages. This will occur even if
138 the number of surplus pages it would exceed the overcommit value. As long as
140 increased sufficiently, or the surplus huge pages go out of use and are freed--
141 no more surplus huge pages will be allowed to be allocated.
170 Whether huge pages are allocated and freed via the /proc interface or
172 nodes from which huge pages are allocated or freed are controlled by the
177 The recommended method to allocate or free huge pages to/from the kernel
188 specified in <node-list>, depending on whether number of persistent huge pages
189 is initially less than or greater than 20, respectively. No huge pages will be
197 persistent huge pages will be distributed across the node or nodes
203 possibly, allocation of persistent huge pages on nodes not allowed by
226 subset of the system nodes to allocate huge pages outside the cpuset
230 of huge pages over all on-lines nodes with memory.
249 of free and surplus [overcommitted] huge pages, respectively, on the parent
252 The nr_hugepages attribute returns the total number of huge pages on the
254 pages on the parent node will be adjusted to the specified value, if sufficient
257 Note that the number of overcommit and reserve pages remain global quantities,
265 If the user applications are going to request huge pages using mmap system
274 /mnt/huge. Any files created on /mnt/huge uses huge pages. The uid and gid
282 size option sets the maximum value of memory (huge pages) allowed for that
286 value of memory (huge pages) allowed for the filesystem. min_size can be
288 huge page pool. At mount time, the number of huge pages specified by
290 free huge pages available, the mount will fail. As huge pages are allocated
292 of allocated and reserved huge pages is always at least min_size. The option
316 Syscalls that operate on memory backed by hugetlb pages only have their lengths
318 errno set to EINVAL or exclude hugetlb pages that extend beyond the length if