Searched refs:surplus (Results 1 – 4 of 4) sorted by relevance
484 size_t const surplus = (alignment > sizeof(void*)) ? alignment - sizeof(void*) : 0; in ZSTD_cwksp_reserve_object_aligned() local485 void* const start = ZSTD_cwksp_reserve_object(ws, byteSize + surplus); in ZSTD_cwksp_reserve_object_aligned()487 if (surplus == 0) return start; in ZSTD_cwksp_reserve_object_aligned()489 return (void*)(((size_t)start + surplus) & ~mask); in ZSTD_cwksp_reserve_object_aligned()
30 and surplus huge pages in the pool of huge pages of default size.57 is short for "surplus," and is the number of huge pages in59 maximum number of surplus huge pages is controlled by62 with each hugetlb page is enabled, the number of surplus huge pages63 may be temporarily larger than the maximum number of surplus huge218 number of "surplus" huge pages from the kernel's normal page pool, when the219 persistent huge page pool is exhausted. As these surplus huge pages become236 of the in-use huge pages to surplus huge pages. This will occur even if237 the number of surplus pages would exceed the overcommit value. As long as240 no more surplus huge pages will be allowed to be allocated.[all …]
152 calls into routines that potentially allocate and adjust surplus page counts.230 brings up the issue of surplus huge pages and overcommit which is beyond231 the scope reservations. Even if a surplus page is allocated, the same
659 writing 0 to nr_hugepages will make any "in use" HugeTLB pages become surplus660 pages. So, those surplus pages are still optimized until they are no longer661 in use. You would need to wait for those surplus pages to be released before