From: Stephen Hemminger <stephen@networkplumber.org>
To: matan@mellanox.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] RFC - vdev_netvsc automatic blacklisting
Date: Tue, 4 Jun 2019 12:54:09 -0700 [thread overview]
Message-ID: <20190604125409.078adf75@hermes.lan> (raw)
When using DPDK on Azure it is common to have one non-DPDK interface.
If that non-DPDK interface is present vdev_netvsc correctly skip it.
But if the non-DPDK has accelerated networking the Mellanox driver will
still get associated with DPDK (and break connectivity).
The current process is to tell users to do whitelist or blacklist the PCI
device(s) not used for DPDK. But vdev_netvsc already is doing a lot of
looking at devices and VF devices.
Could vdev_netvsc just do this automatically by setting devargs for the VF to blacklist?
next reply other threads:[~2019-06-04 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 19:54 Stephen Hemminger [this message]
2019-06-11 6:21 ` Matan Azrad
2019-06-11 14:26 ` Stephen Hemminger
2019-06-12 5:15 ` Matan Azrad
2019-06-12 13:26 ` Stephen Hemminger
2019-06-12 16:13 ` Matan Azrad
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=20190604125409.078adf75@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
/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).