Comment 11 for bug 1826308

Revision history for this message
Yi Wang (wangyi4) wrote :

Cristopher, based on my analysis, I suppose most memory are reserved for hugepage. I have very similar phenomenon with yours. In my deployment, just after controller-0 unlock, the memory jumped from 4G to 156G (the system has 192G in total).

By check /proc/meminfo, I can see it as below. The hugepage size is 2M. So there are 152G reserved in my system.
"
HugePages_Total: 78218
HugePages_Free: 78218
"

I set a smaller number (such as 512) to /proc/sys/vm/nr_hugepages. Then I can get my memory back. Pls check below log.

controller-0:/home/wrsroot# free -h -k
              total used free shared buff/cache available
Mem: 187G 157G 27G 48M 2.6G 28G
Swap: 0B 0B 0B
controller-0:/home/wrsroot# cat /proc/sys/vm/nr_hugepages
78218
controller-0:/home/wrsroot# echo 512 > /proc/sys/vm/nr_hugepages
controller-0:/home/wrsroot# cat /proc/sys/vm/nr_hugepages
512
controller-0:/home/wrsroot# free -h -k
              total used free shared buff/cache available
Mem: 187G 5.5G 179G 48M 2.6G 180G
Swap: 0B 0B 0B
controller-0:/home/wrsroot# echo 78218 > /proc/sys/vm/nr_hugepages
controller-0:/home/wrsroot# cat /proc/sys/vm/nr_hugepages
78218
controller-0:/home/wrsroot# free -h -k
              total used free shared buff/cache available
Mem: 187G 157G 27G 48M 2.6G 28G
Swap: 0B 0B 0B