-
sech1Nice free hashrate boost for most users who failed to configure huge pages: xmrig/xmrig #3743
-
sech1*on Linux
-
DataHoardernote: > Most common kernels configurations provide MADV_HUGEPAGE-style behavior by default, and thus MADV_HUGEPAGE is normally not necessary.
-
DataHoarder> Since Linux 5.4, automatic scan of eligible areas and replacement by huge pages works with private anonymous pages
-
DataHoarderso this might have been done automatically already on 5.4+
-
DataHoarderI tried here with go-randomx, and my pages were already hugepages even when I explicitly did not indicate so, as long as it was MAP_PRIVATE|MAP_ANONYMOUS
-
DataHoarderI didn't check how quick the scan happens, but found that these had been remapped to hugepages as long as the allocation was large/aligned ofc
-
sech1In any case, explicit alignment to a 2 MB and madvise call should cover all possible kernel configurations
-
DataHoarderindeed. adding it covers the cases