Searched refs:surplus (Results 1 – 3 of 3) 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()
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
670 writing 0 to nr_hugepages will make any "in use" HugeTLB pages become surplus671 pages. So, those surplus pages are still optimized until they are no longer672 in use. You would need to wait for those surplus pages to be released before