Lines Matching full:pages

13 using huge pages for the backing of virtual memory with huge pages
53 collapses sequences of basic pages into huge pages.
109 pages unless hugepages are immediately available. Clearly if we spend CPU
111 use hugepages later instead of regular pages. This isn't always
125 	allocation failure and directly reclaim pages and compact
132 	to reclaim pages and wake kcompactd to compact memory so that
134 	of khugepaged to then install the THP pages later.
140 	pages and wake kcompactd to compact memory so that THP is
179 You can also control how many pages khugepaged should scan at each
194 The khugepaged progress can be seen in the number of pages collapsed::
202 ``max_ptes_none`` specifies how many extra small pages (that are
204 of small pages into one large page::
213 ``max_ptes_swap`` specifies how many pages can be brought in from
214 swap when collapsing a group of pages into a transparent huge page::
220 collapsed, resulting fewer pages being collapsed into
223 ``max_ptes_shared`` specifies how many pages can be shared across multiple
245     Attempt to allocate huge pages every time we need a new page;
248     Do not allocate huge pages;
255     Only allocate huge pages if requested with fadvise()/madvise();
260 ``huge=never`` will not attempt to break up huge pages at all, just stop more
288 The number of anonymous transparent huge pages currently used by the
290 To identify what applications are using anonymous transparent huge pages,
294 The number of file transparent huge pages mapped to userspace is available
296 To identify what applications are mapping file transparent huge pages, it
304 monitor how successfully the system is providing huge pages for use.
312 	a range of pages to collapse into one huge page and has
317 	a huge page and instead falls back to using small pages.
321 	instead falls back to using small pages even though the
326 	of pages that should be collapsed into one huge page but failed
335 	but fails and instead falls back to using small pages.
339 	falls back to using small pages even though the allocation was
348 	pages. This can happen for a variety of reasons but a common
359 	splitting it would free up some memory. Pages on split queue are
376 	huge zero page and falls back to using small pages.
387 As the system ages, allocating huge pages may be expensive as the
417 	a huge page aligned range of pages.
422 for huge pages.