Suricata 7.0.2 dpdk: HugePages_Total equals to zero

Nothing changed in an already working suricata 7.0.1 dpdk setup, but suricata 7.0.2 from OISF git master branch runs, but reports: dpdk: HugePages_Total equals to zero

$ suricata -V
This is Suricata version 7.0.2 RELEASE

$ dpdk-proc-info -v
EAL: RTE Version: ‘DPDK 23.07.0’

$ dpdk-devbind.py -s
Network devices using DPDK-compatible driver
============================================
0000:0f:00.0 ‘82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb’ drv=vfio-pci unused=ixgbe
0000:10:00.0 ‘Ethernet Controller E810-C for QSFP 1592’ drv=vfio-pci unused=ice
0000:10:00.1 ‘Ethernet Controller E810-C for QSFP 1592’ drv=vfio-pci unused=ice
0000:84:00.0 ‘Ethernet Controller E810-C for QSFP 1592’ drv=vfio-pci unused=ice
0000:84:00.1 ‘Ethernet Controller E810-C for QSFP 1592’ drv=vfio-pci unused=ice

$ dpdk-hugepages.py -s
Node Pages Size Total
0 8 1Gb 8Gb
1 8 1Gb 8Gb
Hugepages mounted on /dev/hugepages

Hi Andre,
thanks for creating a post here. Unfortunately I somehow overlooked the post at first so that explains the delayed reply.
However, I can see where the problem is, fix is on the way.
In 7.0.2 Suri checks for the presence of hugepages but it only checks /proc/meminfo file which only acknowledges 2MB hugepages. So allocating 1GB hugepages makes no entry in the /proc/meminfo and Suricata then panics for not seeing any hugepages.
Thanks,
Lukas

Hi Lukas,
I was not sure if it impacted Suricata because it still works, or it was more a cosmetic issue.
Thanks!
Andre

No, it does not have an impact on Suricata. The aim was to hint the user that no hugepages are allocated however dpdk-hugepages script is a bit sneaky and allocates 1GB hugepages while not editing the default hugepage size in the meminfo output heh.