> From: Nicholas Pratte [mailto:npra...@iol.unh.edu] > Sent: Thursday, 4 April 2024 17.31 > > The previous implementation configures and allocates hugepage sizes > based on a system default. This can lead to two problems: overallocation > of > hugepages (which may crash the remote host), and configuration of > hugepage > sizes that are not recommended during runtime. This new implementation > allows only 2MB hugepage allocation during runtime; any other unique > hugepage size must be configured by the end-user for initializing DTS. > > If the amount of 2MB hugepages requested exceeds the amount of 2MB > hugepages already configured on the system, then the system will remount > hugepages to cover the difference. If the amount of hugepages requested > is > either less than or equal to the amount already configured on the > system, > then nothing is done. > > Bugzilla ID: 1370 > Signed-off-by: Nicholas Pratte <npra...@iol.unh.edu> > Reviewed-by: Jeremy Spewock <jspew...@iol.unh.edu> > ---
This change seems very CPU specific. E.g. in x86 32-bit mode, the hugepage size is 4 MB, not 2 MB. I don't know the recommended hugepage size on other architectures.
