Project

General

Profile

Bug #6419

Updated by Lukas Sismis about 1 year ago

The current analysis of allocated hugepages only works with /proc/meminfo 
 However this proved insufficient if hugepages are allocated through dpdk-hugepages script and the size of hugepages is not of the default hugepage size. 
 If the default hugepage size is 2 MB kB and the user allocates 1 GB hugepages then these are not shown in the /proc/meminfo output. However, DPDK applications work just fine.  

 Current limitation: 
 - no limitation in functionality 
 - the user sees a message stating that Hugepage_Total is zero while Suricata runs. 

 First reported at: 
 https://forum.suricata.io/t/suricata-7-0-2-dpdk-hugepages-total-equals-to-zero/4071/3

Back