From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 66] Secondary process must have exact same whitelist "-w" list
Date: Mon, 25 Jun 2018 16:51:59 +0000 [thread overview]
Message-ID: <bug-66-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=66
Bug ID: 66
Summary: Secondary process must have exact same whitelist "-w"
list
Product: DPDK
Version: 18.05
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: minor
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: tom.barbette@uliege.be
Target Milestone: ---
When a primary process is launched with some whitelisted PCIe devices, the
secondary process will not detect NICs if the exact same whitelisting
parameters are not given.
Eg, if I pass :
sudo ./testpmd -w 01:00.0 -w 01:00.1 --proc-type primary --
Then if I just run sudo ./testpmd --proc-type secondary --
I will have :
EAL: PCI device 0000:01:00.0 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: secondary process attach failed, ethdev doesn't existEAL: Requested device
0000:01:00.0 cannot be used
EAL: PCI device 0000:01:00.1 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: secondary process attach failed, ethdev doesn't existEAL: Requested device
0000:01:00.1 cannot be used
EAL: PCI device 0000:03:00.0 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
...
I would personally expect the secondaries to be able to open only the
whitelisted in the secondary, or maybe all devices.
If I launch the secondary with the same -w, the secondary will be able to
access the devices as expected :
sudo ./testpmd -w 01:00.0 -w 01:00.1 --proc-type secondary --
EAL: PCI device 0000:01:00.0 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:01:00.1 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
Thanks,
Tom
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-06-25 16:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-66-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).