DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] tools/dpdk_nic_bind: Fix can't bind	virtio-pci issue
Date: Thu, 05 Mar 2015 21:31:37 +0100	[thread overview]
Message-ID: <118801828.6UbpCNZDcL@xps13> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E60286CEE857@SHSMSX101.ccr.corp.intel.com>

> > The dpdk_nic_bind script will not allow ports to be bound or unbound if none of the
> > kernel modules supported by DPDK is loaded. This patch relaxes this restriction by
> > checking if a DPDK module is actually requested. The example below illustrates this
> > problem:
> >
> > In virtio test, on the guest
> > 1. Bind virtio port to igb_uio driver;
> > 2. Remove igb_uio module;
> > 3. Bind virtio port to virtio-pci driver, it fails and reports:
> >    "Error - no supported modules are loaded"
> >
> > The script should check the to-be-bound driver flag, if it is dpdk driver(igb_uio, vfio etc),
> > and the corresponding module is not loaded, then exit, otherwise, just report a warning,
> > and continue to bind the non-dpdk driver(like virtio-pci) to dev.
> >
> > Signed-off-by: Changchun Ouyang <changchun.ouyang@intel.com>
> Acked-by: Michael Qiu <michael.qiu@intel.com>

Applied, thanks

      reply	other threads:[~2015-03-05 20:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  4:57 [dpdk-dev] [PATCH] " Ouyang Changchun
2015-02-26  5:52 ` Xu, Qian Q
2015-03-03 11:43 ` Bruce Richardson
2015-03-04  2:41   ` Ouyang, Changchun
2015-03-04  2:55 ` [dpdk-dev] [PATCH v2] " Ouyang Changchun
2015-03-04 11:31   ` Qiu, Michael
2015-03-05 20:31     ` 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=118801828.6UbpCNZDcL@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=changchun.ouyang@intel.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 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).