From: Franck Baudin <franck.baudin@qosmos.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: virtio-net: bind systematically on all non blacklisted virtio-net devices
Date: Tue, 8 Sep 2015 10:23:26 +0200 [thread overview]
Message-ID: <55EE9AFE.1070202@qosmos.com> (raw)
Hi,
virtio-net driver bind on all virtio-net devices, even if the devices
are used by the kernel (leading to kernel soft-lookup/panic). One way
around is to blacklist the ports in use by Linux. This is the case since
v2.0.0, in fact since commit da978dfdc43b59e290a46d7ece5fd19ce79a1162
and the removal of the RTE_PCI_DRV_NEED_MAPPING driver flag.
Questions:
1/ Is it the expected behaviour?
2/ Why is it different from vmxnet3 pmd? In other words, should't
we re-add the RTE_PCI_DRV_NEED_MAPPING to virtio pmd or remove it from
pmxnet3 pmd?
3/ If this is the expected behaviour, shouldn't we update
dpdk_nic_bind.py (binding status irrelevant for virtio) tool and the
documentation (mentioning igb_uio while misleading and useless)?
Thanks!
Best Regards,
Franck
next reply other threads:[~2015-09-08 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 8:23 Franck Baudin [this message]
2015-09-09 2:11 ` virtio-net: bind systematically on all non blacklisted virtio-net devices Ouyang, Changchun
2015-09-10 12:30 ` Franck Baudin
2015-10-01 15:08 ` Thomas Monjalon
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=55EE9AFE.1070202@qosmos.com \
--to=franck.baudin@qosmos.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.