Hi, I have exhausted all my options and want to reach out to the dpdk developers for guidance.
My situation is as follows: We were on DPDK 17.11.6 and upgraded to DPDK22.11.2 to support the Intel E810. Also upgraded from CentOS7 to Oracle 91. In DPDK 22.11.2 the VIRT memory has skyrocketed and causes major issues with our application that runs on 16 GB of memory (virtual appliances and low end remote appliances). I have also tried DPDK 23.11 and 24.03 and I also see across the DPDK versions that the VIRT memory has increase by a factor of 5 over DPDK 17.11 Our application process shows VIRT memory is 7.6 GB with DPDK 17.11.6, and with DPDK 22.11.2, 23.11.2 and 24.03 the VIRT memory is ~36.6GB Our application minimum configuration needs to run with 16 GB memory when DPDK is enabled. Our application uses memory locking and rlimit settings to get optimal performance. I understand that DPDK memory design has changed since DPDK 18.xx. We don't use hot-plug feature, encryption, security, telemetry, ipsec, or graph. Currently we configure 2x1G hugepages and single socket. I have tried to disable telemetry, cryptodev, etc in meson and only to find they can not be disabled, they are mandatory. rte_eal_init() has argument "--legacy-mem", which brought down the VIRT memory to 36.6GB, but not enough. Is there a developer guide to attack this problem in very low risk and timely fashion? Thank you, Ed
