Hello, I am in the process of upgrading my application from DPDK 18.11 to 20.11.1. My particular application is slightly unusual in that I am calling DPDK from Java using JNI. This has worked previously in 18.11.
When I run my application under 20.11.1 I get the output shown below before it crashes with a coredump at my call to rte_eth_rx_burst(). I suspect that the issue is related to the warning messages, as they don't appear if I run the application directly (i.e. bypassing Java JNI). EAL: Detected 24 lcore(s) EAL: Detected 2 NUMA nodes EAL: Static memory layout is selected, amount of reserved memory can be adjusted with -m or --socket-mem EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: Probing VFIO support... EAL: VFIO support initialized EAL: WARNING! Base virtual address hint (0x240036000 != 0x7f7c80000000) not respected! EAL: This may cause issues with mapping memory into secondary processes EAL: WARNING! Base virtual address hint (0x3c0037000 != 0x7f7440000000) not respected! EAL: This may cause issues with mapping memory into secondary processes EAL: WARNING! Base virtual address hint (0x540038000 != 0x7f6c00000000) not respected! EAL: This may cause issues with mapping memory into secondary processes EAL: WARNING! Base virtual address hint (0x6c0039000 != 0x7f63c0000000) not respected! EAL: This may cause issues with mapping memory into secondary processes EAL: PCI device 0000:41:00.0 on NUMA socket 1 EAL: probe driver: 8086:154d net_ixgbe EAL: PCI device 0000:41:00.1 on NUMA socket 1 EAL: probe driver: 8086:154d net_ixgbe EAL: PCI device 0000:42:00.0 on NUMA socket 1 EAL: probe driver: 8086:154d net_ixgbe EAL: PCI device 0000:42:00.1 on NUMA socket 1 EAL: probe driver: 8086:154d net_ixgbe Is there some EAL argument I can provide to avoid this coredump? Thanks! Gavan
