DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Franck Baudin <franck.baudin@qosmos.com>,
	"Ouyang, Changchun" <changchun.ouyang@intel.com>,
	huawei.xie@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] virtio-net: bind systematically on all non blacklisted virtio-net devices
Date: Thu, 01 Oct 2015 17:08:05 +0200	[thread overview]
Message-ID: <1569737.1ykgx8Ghpo@xps13> (raw)
In-Reply-To: <55F177D4.5010701@qosmos.com>

2015-09-10 14:30, Franck Baudin:
> On 09/09/15 04:11, Ouyang, Changchun wrote:
> >> 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.
> 
> Thanks for your answer,
> 
> So this is the expected behaviour: all virtio interfaces are bound to 
> the pmd driver.
> 
> Don't you think that dpdk_nic_bind.py should reflect the driver 
> behaviour, and that the virtio documentation (still referencing igb_uio) 
> be amended?

Yes maybe that the documentation must be updated.
Anyone?

      reply	other threads:[~2015-10-01 15:09 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
2015-09-10 12:30   ` Franck Baudin
2015-10-01 15:08     ` Thomas Monjalon [this message]

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=1569737.1ykgx8Ghpo@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=changchun.ouyang@intel.com \
    --cc=dev@dpdk.org \
    --cc=franck.baudin@qosmos.com \
    --cc=huawei.xie@intel.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).