From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: Franck Baudin <franck.baudin@qosmos.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] virtio-net: bind systematically on all non blacklisted virtio-net devices
Date: Wed, 9 Sep 2015 02:11:47 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511D06B61@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <55EE9AFE.1070202@qosmos.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Franck Baudin
> Sent: Tuesday, September 8, 2015 4:23 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] virtio-net: bind systematically on all non blacklisted
> virtio-net devices
>
> 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.
It allows virtio-pmd not necessarily depend on igb_uio, this is which characteristic other pmd drivers don't have.
>
> 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 prev parent reply other threads:[~2015-09-09 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 8:23 Franck Baudin
2015-09-09 2:11 ` Ouyang, Changchun [this message]
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=F52918179C57134FAEC9EA62FA2F962511D06B61@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=franck.baudin@qosmos.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).