From: waqas ahmed <waqasahmed1471@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Invalid NUMA socket
Date: Sun, 26 Aug 2018 11:04:25 +0500 [thread overview]
Message-ID: <CAMr3K=eLNFsgC8HXJu1dE-TcZrtnNMoxgVvyvUHf6haz1GRvYg@mail.gmail.com> (raw)
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
next reply other threads:[~2018-08-26 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 6:04 waqas ahmed [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMr3K=eLNFsgC8HXJu1dE-TcZrtnNMoxgVvyvUHf6haz1GRvYg@mail.gmail.com' \
--to=waqasahmed1471@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).