Re: [dpdk-users] Invalid NUMA socket

["Wiles, Keith" <keith.wiles@intel.com>]

> 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