How to enable 1G hugepages?

[huggy3233]

I've been trying to enable 1G hugepages on my proxmox server (R7 5700X, 48GB RAM, Proxmox 7.4, Kernel: 6.2.11-2-pve) but haven't been able to get it to work. I am aiming to allocate 16 1Gibibyte hugepages to a vm for a total of 16 Gibibytes. So far I have added: hugepagesz=1G hugepages=16 default_hugepagesz=1G to my grub boot parameters, and added: hugepages: 1024 to my vms config. When running hugeadm --explain it appears that the pages have been created successfully. But when I run this command: grep -e AnonHugePages /proc/*/smaps | awk '{ if($2>4) print $0} ' | awk -F "/" '{print $0; system("ps -fp " $3)} ' to check which processes are using hugepages my vm is still using 2M pages.

What am I doing wrong here? or is that check command not the proper way to check hugepage allocation?

 

[LnxBil]

grep -e AnonHugePages /proc/*/smaps | awk '{ if($2>4) print $0} ' | awk -F "/" '{print $0; system("ps -fp " $3)} ' to check which processes are using hugepages my vm is still using 2M pages.

You grep for anonymous hugepages, If you configure hugepages, they are not anonymous anymore.

 

[huggy3233]

What is the difference between anonymous and normal hugepages?
How do I check for normal hugepage usage?

 

[LnxBil]

What is the difference between anonymous and normal hugepages?

normal hugepages are allocated manually and anonymous hugepages are allocated in the background and on demand. They are a little bit unpredictable and often people advice in deactivating them completely. Once allocated, they cannot be used by normal processes and only a fraction of all programs can use hugepages. One of them is KVM, so therefore it may be an advantage of using them.

I personally work a lot with hugepages, yet with databases, not especially with VMs. Hugepages are often only allocatable before the memory is filled and fragmented, so you may require a reboot on online/live hugepage increase.

How do I check for normal hugepage usage?

Normalle via /proc/meminfo (general) or via smap similar as you did:

 grep -B 11 -E 'KernelPageSize:\s+2048 kB' /proc/$PID/smaps | grep "^Size:" | awk 'BEGIN{sum=0}{sum+=$2}END{print sum/2048}'

 

[huggy3233]

Running that command for my vm's process returns 0, what does that mean in this case?

 

[LnxBil]

Running that command for my vm's process returns 0, what does that mean in this case?

What does cat /proc/meminfo show? Have you configured your VM to use hugepages? This is not done automatically.

 

[huggy3233]

/proc/meminfo shows that I have 16 1Gib hugepages, in my vms .conf file I have added hugepages: 1024.

 

[LnxBil]

Have you enabled the hardware cpu flag pdpe1gb? This may also be necessary.

 

[huggy3233]

That flag is enabled, I think the problem here is that I am unsure how to check if hugepages are working properly.

 

[LnxBil]

That flag is enabled, I think the problem here is that I am unsure how to check if hugepages are working properly.

Check /proc/meminfo, it shows if they're used or not.

 

[huggy3233]

There are no free hugepages so I guess they are being used, if I restart the vm will the hugepages still work?

 

[LnxBil]

There are no free hugepages so I guess they are being used, if I restart the vm will the hugepages still work?

The free counter should increase (stop) and be reused if you start the VM again.

 

[LnxBil]

 grep -B 11 -E 'KernelPageSize:\s+2048 kB' /proc/$PID/smaps | grep "^Size:" | awk 'BEGIN{sum=0}{sum+=$2}END{print sum/2048}'

You should grep the smap what other Kernel page sizes are there and change it respectively.

 

[huggy3233]

Changing the command to the correct sizes returns 16, which I assume is the correct result. Hugepages are also working after a restart. Thanks for your help.

 

[LnxBil]

Thanks for your help.

Glad it worked.