DPDK usage discussions
 help / color / mirror / Atom feed
From: Devanath S <s.devanath@gmail.com>
To: dpdk-ovs@lists.01.org, "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] netdev-dpdk: add hotplug support
Date: Sun, 12 Feb 2017 22:25:00 -0800	[thread overview]
Message-ID: <CADjMg7UhFGyjO5=wKmJGMN9GEOQaEpGdHRGdq+XpW17at4_Oeg@mail.gmail.com> (raw)

Hi,


I am looking for the below feature in ovs, with 2.6.1 release it seem
to fail.  I dont see any reference to rte_eth_dev_attach()/detach()api
in the code aswell. Even though ovs 2.6 release note indicates the
support, the feature doesnt seem to work. Please advice.

Ovs How_to documentation
=========================
http://docs.openvswitch.org/en/latest/howto/dpdk
OVS supports port hotplugging, allowing the use of ports that were not
bound to DPDK when vswitchd was started. In order to attach a port, it
has to be bound to DPDK using the dpdk_nic_bind.py script: $
$DPDK_DIR/tools/dpdk_nic_bind.py --bind=igb_uio 0000:01:00.0 Then it
can be attached to OVS: $ ovs-vsctl add-port br0 dpdkx -- set
Interface dpdkx type=dpdk \ options:dpdk-devargs=0000:01:00.0 It is
also possible to detach a port from ovs, the user has to remove the
port using the del-port command, then it can be detached using: $
ovs-appctl netdev-dpdk/detach 0000:01:00.0 This feature is not
supported with VFIO and does not work with some NICs. For more
information please refer to the DPDK Port Hotplug Framework.

Code commit of the feature:
----------------------------------------
commit b8374d0d04260793db35b617eb15bba958d50003
Author: Mauricio Vásquez <mauricio.vasquezbernal@studenti.polito.it>
Date:   Thu Jan 5 10:42:08 2017 +0000

    netdev-dpdk: add hotplug support

    In order to use dpdk ports in ovs they have to be bound to a DPDK
    compatible driver before ovs is started.

    This patch adds the possibility to hotplug (or hot-unplug) a device
    after ovs has been started. The implementation adds two appctl commands:
    netdev-dpdk/attach and netdev-dpdk/detach

    After the user attaches a new device, it has to be added to a bridge
    using the add-port command, similarly, before detaching a device,
    it has to be removed using the del-port command.

    Signed-off-by: Mauricio Vasquez B
<mauricio.vasquezbernal@studenti.polito.it>
    Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
    Co-authored-by: Ciara Loftus <ciara.loftus@intel.com>
    Acked-by: Stephen Finucane <stephen@that.guru>  # docs only
    Signed-off-by: Daniele Di Proietto <diproiettod@vmware.com>

                 reply	other threads:[~2017-02-13  6:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CADjMg7UhFGyjO5=wKmJGMN9GEOQaEpGdHRGdq+XpW17at4_Oeg@mail.gmail.com' \
    --to=s.devanath@gmail.com \
    --cc=dpdk-ovs@lists.01.org \
    --cc=users@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).