Lines Matching refs:HugeTLB

572 Enable (set to 1) or disable (set to 0) HugeTLB Vmemmap Optimization (HVO).
574 Once enabled, the vmemmap pages of subsequent allocation of HugeTLB pages from
575 buddy allocator will be optimized (7 pages per 2MB HugeTLB page and 4095 pages
576 per 1GB HugeTLB page), whereas already allocated HugeTLB pages will not be
577 optimized.  When those optimized HugeTLB pages are freed from the HugeTLB pool
580 again.  If your use case is that HugeTLB pages are allocated 'on the fly' (e.g.
581 never explicitly allocating HugeTLB pages with 'nr_hugepages' but only set
582 'nr_overcommit_hugepages', those overcommitted HugeTLB pages are allocated 'on
583 the fly') instead of being pulled from the HugeTLB pool, you should weigh the
585 of allocation or freeing HugeTLB pages between the HugeTLB pool and the buddy
587 pressure, it could prevent the user from freeing HugeTLB pages from the HugeTLB
591 Once disabled, the vmemmap pages of subsequent allocation of HugeTLB pages from
593 time from buddy allocator disappears, whereas already optimized HugeTLB pages
594 will not be affected.  If you want to make sure there are no optimized HugeTLB
596 writing 0 to nr_hugepages will make any "in use" HugeTLB pages become surplus