Hello DPDK devs, I've meson built (using just meson build && ninja -C build) dpdk-20.08 (downloaded from the site) on a Taishan arm server and dpdk-testpmd is incorrectly detecting NUMA nodes on the system: EAL: Detected 16 lcore(s) EAL: Detected 1 NUMA nodes
lscpu report 4 NUMA nodes: NUMA node0 CPU(s): 0-15 NUMA node1 CPU(s): 16-31 NUMA node2 CPU(s): 32-47 NUMA node3 CPU(s): 48-63 When built with make T=arm64-armv8a-linuxapp-gcc testpmd is detecting NUMA nodes correctly: EAL: Detected 64 lcore(s) EAL: Detected 4 NUMA nodes Any idea what's the difference between the builds? I've looked at NUMA config options but those seem ok to me: grep NUMA arm64-armv8a-linuxapp-gcc/.config build/rte_build_config.h arm64-armv8a-linuxapp-gcc/.config:CONFIG_RTE_MAX_NUMA_NODES=8 arm64-armv8a-linuxapp-gcc/.config:# a "type" is a combination of page size and NUMA node. total number of memseg arm64-armv8a-linuxapp-gcc/.config:CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=y arm64-armv8a-linuxapp-gcc/.config:CONFIG_RTE_LIBRTE_VHOST_NUMA=y build/rte_build_config.h:#define RTE_EAL_NUMA_AWARE_HUGEPAGES 1 build/rte_build_config.h:#define RTE_HAS_LIBNUMA 1 build/rte_build_config.h:#define RTE_LIBRTE_VHOST_NUMA 1 build/rte_build_config.h:#define RTE_MAX_NUMA_NODES 4 Any pointers are welcome. Thanks, Juraj
