> On Dec 20, 2017, at 9:14 AM, Stephen Hemminger <[email protected]> > wrote: > > On Wed, 20 Dec 2017 16:56:00 +0900 > 박준하<[email protected]> wrote: > >> Thank you Shreyansh Jain. >> I tried to change -n 1 but i got same problem. >> this is log. >> >> root@jh-desktop:/home/jh/dpdk-17.11/examples/helloworld# >> ./build/app/helloworld -l 0-3 -n 1 >> EAL: Detected 4 lcore(s) >> EAL: Probing VFIO support... >> EAL: PCI device 0000:00:1f.6 on NUMA socket -1 >> EAL: Invalid NUMA socket, default to 0 >> EAL: probe driver: 8086:15b8 net_e1000_em >> EAL: PCI device 0000:01:00.0 on NUMA socket -1 >> EAL: Invalid NUMA socket, default to 0 >> EAL: probe driver: 8086:1528 net_ixgbe >> EAL: PCI device 0000:01:00.1 on NUMA socket -1 >> EAL: Invalid NUMA socket, default to 0 >> EAL: probe driver: 8086:1528 net_ixgbe >> hello from core 1 >> hello from core 2 >> hello from core 3 >> hello from core 0 >> > > > Ignore the warning "Invalid NUMA socket" it is meaningless. > If the platform does not support NUMA or kernel is compiled without NUMA > support > than the sysfs file for numa node is not present, and DPDK applications > default > to all 0
This is a case were the message Invalid NUMA should be changed to a DEBUG log and the ‘on NUMA socket -1’ should just report 0 not -1. Regards, Keith
