* [dpdk-users] Invalid NUMA socket @ 2018-08-26 6:04 waqas ahmed 2018-08-26 14:52 ` Wiles, Keith 0 siblings, 1 reply; 5+ messages in thread From: waqas ahmed @ 2018-08-26 6:04 UTC (permalink / raw) To: users Hi everyone, we have dual socket xeon cpu, and we have intel 52899 10g nic having pci address 0000:05:00.0. while running helloworld app EAL log tells that this device is found on numa socket -1 ! it should be found on either numa node 0 or 1? ------------------------------------------------------------------------ numactl --hardware gives following output available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 node 0 size: 16036 MB node 0 free: 10268 MB node 1 cpus: 4 5 6 7 node 1 size: 16125 MB node 1 free: 11977 MB node distances: node 0 1 0: 10 21 1: 21 10 DPDK helloworld app log --------------------------------------------------------------------------- EAL: Detected 8 lcore(s) EAL: Multi-process socket /var/run/.rte_unix EAL: Probing VFIO support... EAL: PCI device 0000:01:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10c9 net_e1000_igb EAL: PCI device 0000:01:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10c9 net_e1000_igb EAL: PCI device 0000:05:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe EAL: PCI device 0000:05:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe hello from core 2 hello from core 3 hello from core 4 hello from core 5 hello from core 6 hello from core 7 hello from core 1 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-users] Invalid NUMA socket 2018-08-26 6:04 [dpdk-users] Invalid NUMA socket waqas ahmed @ 2018-08-26 14:52 ` Wiles, Keith 2018-08-26 17:38 ` waqas ahmed 0 siblings, 1 reply; 5+ messages in thread From: Wiles, Keith @ 2018-08-26 14:52 UTC (permalink / raw) To: waqas ahmed; +Cc: users > On Aug 26, 2018, at 1:04 AM, waqas ahmed <waqasahmed1471@gmail.com> wrote: > > Hi everyone, > we have dual socket xeon cpu, and we have intel 52899 10g nic having pci > address 0000:05:00.0. while running helloworld app EAL log tells that this > device is found on numa socket -1 ! it should be found on either numa node > 0 or 1? > ------------------------------------------------------------------------ > numactl --hardware gives following output > available: 2 nodes (0-1) > node 0 cpus: 0 1 2 3 > node 0 size: 16036 MB > node 0 free: 10268 MB > node 1 cpus: 4 5 6 7 > node 1 size: 16125 MB > node 1 free: 11977 MB > node distances: > node 0 1 > 0: 10 21 > 1: 21 10 Can you tell us the version of DPDK and the OS/version. I assume you are not running inside a VM, right? > > DPDK helloworld app log > --------------------------------------------------------------------------- > EAL: Detected 8 lcore(s) > EAL: Multi-process socket /var/run/.rte_unix > EAL: Probing VFIO support... > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10c9 net_e1000_igb > EAL: PCI device 0000:01:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10c9 net_e1000_igb > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > hello from core 2 > hello from core 3 > hello from core 4 > hello from core 5 > hello from core 6 > hello from core 7 > hello from core 1 You can also change the hello world app and call rte_socket_id() and print that value out too? Regards, Keith ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-users] Invalid NUMA socket 2018-08-26 14:52 ` Wiles, Keith @ 2018-08-26 17:38 ` waqas ahmed 2018-08-26 17:48 ` Wiles, Keith 0 siblings, 1 reply; 5+ messages in thread From: waqas ahmed @ 2018-08-26 17:38 UTC (permalink / raw) To: keith.wiles, users many thanks keith for help here are the details dpdk-18.02.2 $> lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $> uname -r 4.10.0-19-generic ---------------------------------------- following is the output by calling rte_socket_id(), which associate lcores to their numa socket correctly, i am just got curious about why nic is not associated with its numa socket! i am working on remote server. ---------------------------------------- EAL: Detected 8 lcore(s) EAL: Multi-process socket /var/run/.rte_unix EAL: Probing VFIO support... EAL: PCI device 0000:01:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10c9 net_e1000_igb EAL: PCI device 0000:01:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10c9 net_e1000_igb EAL: PCI device 0000:05:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe EAL: PCI device 0000:05:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe hello from core 1 on socket 0 hello from core 2 on socket 0 hello from core 3 on socket 0 hello from core 4 on socket 1 hello from core 5 on socket 1 hello from core 6 on socket 1 hello from core 7 on socket 1 hello from core 0 on socket 0 ------------------------------------------------- Regards Ahmed On Sun, Aug 26, 2018 at 7:52 PM Wiles, Keith <keith.wiles@intel.com> wrote: > > > > On Aug 26, 2018, at 1:04 AM, waqas ahmed <waqasahmed1471@gmail.com> > wrote: > > > > Hi everyone, > > we have dual socket xeon cpu, and we have intel 52899 10g nic having pci > > address 0000:05:00.0. while running helloworld app EAL log tells that > this > > device is found on numa socket -1 ! it should be found on either numa > node > > 0 or 1? > > ------------------------------------------------------------------------ > > numactl --hardware gives following output > > available: 2 nodes (0-1) > > node 0 cpus: 0 1 2 3 > > node 0 size: 16036 MB > > node 0 free: 10268 MB > > node 1 cpus: 4 5 6 7 > > node 1 size: 16125 MB > > node 1 free: 11977 MB > > node distances: > > node 0 1 > > 0: 10 21 > > 1: 21 10 > > Can you tell us the version of DPDK and the OS/version. > > I assume you are not running inside a VM, right? > > > > > DPDK helloworld app log > > > --------------------------------------------------------------------------- > > EAL: Detected 8 lcore(s) > > EAL: Multi-process socket /var/run/.rte_unix > > EAL: Probing VFIO support... > > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10c9 net_e1000_igb > > EAL: PCI device 0000:01:00.1 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10c9 net_e1000_igb > > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10fb net_ixgbe > > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10fb net_ixgbe > > hello from core 2 > > hello from core 3 > > hello from core 4 > > hello from core 5 > > hello from core 6 > > hello from core 7 > > hello from core 1 > > You can also change the hello world app and call rte_socket_id() and print > that value out too? > > Regards, > Keith > > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-users] Invalid NUMA socket 2018-08-26 17:38 ` waqas ahmed @ 2018-08-26 17:48 ` Wiles, Keith 2018-08-26 20:48 ` Stephen Hemminger 0 siblings, 1 reply; 5+ messages in thread From: Wiles, Keith @ 2018-08-26 17:48 UTC (permalink / raw) To: waqas ahmed; +Cc: users > On Aug 26, 2018, at 12:38 PM, waqas ahmed <waqasahmed1471@gmail.com> wrote: > > many thanks keith for help > here are the details > dpdk-18.02.2 > $> lsb_release -a > Distributor ID: Ubuntu > Description: Ubuntu 17.04 > Release: 17.04 > Codename: zesty > $> uname -r > 4.10.0-19-generic > ---------------------------------------- > following is the output by calling rte_socket_id(), which associate lcores to their numa socket correctly, i am just got curious about why nic is not associated with its numa socket! > i am working on remote server. Well I assume it should be working too, but I would start by looking at the code that prints out the -1 value. > ---------------------------------------- > EAL: Detected 8 lcore(s) > EAL: Multi-process socket /var/run/.rte_unix > EAL: Probing VFIO support... > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10c9 net_e1000_igb > EAL: PCI device 0000:01:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10c9 net_e1000_igb > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > hello from core 1 on socket 0 > hello from core 2 on socket 0 > hello from core 3 on socket 0 > hello from core 4 on socket 1 > hello from core 5 on socket 1 > hello from core 6 on socket 1 > hello from core 7 on socket 1 > hello from core 0 on socket 0 > ------------------------------------------------- > Regards > Ahmed > > > On Sun, Aug 26, 2018 at 7:52 PM Wiles, Keith <keith.wiles@intel.com> wrote: > > > > On Aug 26, 2018, at 1:04 AM, waqas ahmed <waqasahmed1471@gmail.com> wrote: > > > > Hi everyone, > > we have dual socket xeon cpu, and we have intel 52899 10g nic having pci > > address 0000:05:00.0. while running helloworld app EAL log tells that this > > device is found on numa socket -1 ! it should be found on either numa node > > 0 or 1? > > ------------------------------------------------------------------------ > > numactl --hardware gives following output > > available: 2 nodes (0-1) > > node 0 cpus: 0 1 2 3 > > node 0 size: 16036 MB > > node 0 free: 10268 MB > > node 1 cpus: 4 5 6 7 > > node 1 size: 16125 MB > > node 1 free: 11977 MB > > node distances: > > node 0 1 > > 0: 10 21 > > 1: 21 10 > > Can you tell us the version of DPDK and the OS/version. > > I assume you are not running inside a VM, right? > > > > > DPDK helloworld app log > > --------------------------------------------------------------------------- > > EAL: Detected 8 lcore(s) > > EAL: Multi-process socket /var/run/.rte_unix > > EAL: Probing VFIO support... > > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10c9 net_e1000_igb > > EAL: PCI device 0000:01:00.1 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10c9 net_e1000_igb > > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10fb net_ixgbe > > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10fb net_ixgbe > > hello from core 2 > > hello from core 3 > > hello from core 4 > > hello from core 5 > > hello from core 6 > > hello from core 7 > > hello from core 1 > > You can also change the hello world app and call rte_socket_id() and print that value out too? > > Regards, > Keith > Regards, Keith ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-users] Invalid NUMA socket 2018-08-26 17:48 ` Wiles, Keith @ 2018-08-26 20:48 ` Stephen Hemminger 0 siblings, 0 replies; 5+ messages in thread From: Stephen Hemminger @ 2018-08-26 20:48 UTC (permalink / raw) To: Wiles, Keith; +Cc: waqas ahmed, users On Sun, 26 Aug 2018 17:48:04 +0000 "Wiles, Keith" <keith.wiles@intel.com> wrote: > > On Aug 26, 2018, at 12:38 PM, waqas ahmed <waqasahmed1471@gmail.com> wrote: > > > > many thanks keith for help > > here are the details > > dpdk-18.02.2 > > $> lsb_release -a > > Distributor ID: Ubuntu > > Description: Ubuntu 17.04 > > Release: 17.04 > > Codename: zesty > > $> uname -r > > 4.10.0-19-generic > > ---------------------------------------- > > following is the output by calling rte_socket_id(), which associate lcores to their numa socket correctly, i am just got curious about why nic is not associated with its numa socket! > > i am working on remote server. > > Well I assume it should be working too, but I would start by looking at the code that prints out the -1 value. > > > ---------------------------------------- > > EAL: Detected 8 lcore(s) > > EAL: Multi-process socket /var/run/.rte_unix > > EAL: Probing VFIO support... > > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10c9 net_e1000_igb > > EAL: PCI device 0000:01:00.1 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10c9 net_e1000_igb > > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10fb net_ixgbe > > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > > EAL: Invalid NUMA socket, default to 0 > > EAL: probe driver: 8086:10fb net_ixgbe > > hello from core 1 on socket 0 > > hello from core 2 on socket 0 > > hello from core 3 on socket 0 > > hello from core 4 on socket 1 > > hello from core 5 on socket 1 > > hello from core 6 on socket 1 > > hello from core 7 on socket 1 > > hello from core 0 on socket 0 > > ------------------------------------------------- > > Regards > > Ahmed > > > > > > On Sun, Aug 26, 2018 at 7:52 PM Wiles, Keith <keith.wiles@intel.com> wrote: > > > > > > > On Aug 26, 2018, at 1:04 AM, waqas ahmed <waqasahmed1471@gmail.com> wrote: > > > > > > Hi everyone, > > > we have dual socket xeon cpu, and we have intel 52899 10g nic having pci > > > address 0000:05:00.0. while running helloworld app EAL log tells that this > > > device is found on numa socket -1 ! it should be found on either numa node > > > 0 or 1? > > > ------------------------------------------------------------------------ > > > numactl --hardware gives following output > > > available: 2 nodes (0-1) > > > node 0 cpus: 0 1 2 3 > > > node 0 size: 16036 MB > > > node 0 free: 10268 MB > > > node 1 cpus: 4 5 6 7 > > > node 1 size: 16125 MB > > > node 1 free: 11977 MB > > > node distances: > > > node 0 1 > > > 0: 10 21 > > > 1: 21 10 > > > > Can you tell us the version of DPDK and the OS/version. > > > > I assume you are not running inside a VM, right? > > > > > > > > DPDK helloworld app log > > > --------------------------------------------------------------------------- > > > EAL: Detected 8 lcore(s) > > > EAL: Multi-process socket /var/run/.rte_unix > > > EAL: Probing VFIO support... > > > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > > > EAL: Invalid NUMA socket, default to 0 > > > EAL: probe driver: 8086:10c9 net_e1000_igb > > > EAL: PCI device 0000:01:00.1 on NUMA socket -1 > > > EAL: Invalid NUMA socket, default to 0 > > > EAL: probe driver: 8086:10c9 net_e1000_igb > > > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > > > EAL: Invalid NUMA socket, default to 0 > > > EAL: probe driver: 8086:10fb net_ixgbe > > > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > > > EAL: Invalid NUMA socket, default to 0 > > > EAL: probe driver: 8086:10fb net_ixgbe > > > hello from core 2 > > > hello from core 3 > > > hello from core 4 > > > hello from core 5 > > > hello from core 6 > > > hello from core 7 > > > hello from core 1 > > > > You can also change the hello world app and call rte_socket_id() and print that value out too? > > > > Regards, > > Keith > > > > Regards, > Keith > DPDK is getting numa socket from sysfs. Make sure your kernel is compiled with NUMA support, and look at /sys/bus/pci/devices to check for numa_node file. ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-08-26 20:48 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-08-26 6:04 [dpdk-users] Invalid NUMA socket waqas ahmed 2018-08-26 14:52 ` Wiles, Keith 2018-08-26 17:38 ` waqas ahmed 2018-08-26 17:48 ` Wiles, Keith 2018-08-26 20:48 ` Stephen Hemminger
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).