Lines Matching +full:tlb +full:- +full:split

28 requiring larger clear-page copy-page in page faults which is a
38 1) the TLB miss will run faster (especially with virtualization using
42 2) a single TLB entry will be mapping a much larger amount of virtual
43    memory in turn reducing the number of TLB misses. With
44    virtualization and nested pagetables the TLB can be mapped of
47    the two is using hugepages just because of the fact the TLB miss is
78 possible to disable hugepages system-wide and to only have them inside
95 -------------------
149 	should be self-explanatory.
168 -------------------
259 ``mount -o remount,huge= /mountpoint`` works fine after mount: remounting
275     Force the huge option on for all - very useful for testing;
347 	is incremented every time a huge page is split into base
353 	is incremented if kernel fails to split huge
357 	is incremented when a huge page is put onto split
359 	splitting it would free up some memory. Pages on split queue are
360 	going to be split under memory pressure.
363 	is incremented every time a PMD split into table of PTEs.
365 	munmap() on part of huge page. It doesn't split huge page, only
383 	is incremented if a huge page has to be split before swapout.