diff options
| author | Ciara Loftus <ciara.loftus@intel.com> | 2017-01-05 10:42:09 +0000 |
|---|---|---|
| committer | Daniele Di Proietto <diproiettod@vmware.com> | 2017-01-05 20:10:13 -0800 |
| commit | 55e075e65ef9ecbd70e5e0fada2704c3d73724d8 (patch) | |
| tree | cee33f674f733cf432ab80856d443d3809871c52 /Documentation | |
| parent | b8374d0d04260793db35b617eb15bba958d50003 (diff) | |
| download | openvswitch-55e075e65ef9ecbd70e5e0fada2704c3d73724d8.tar.gz | |
netdev-dpdk: Arbitrary 'dpdk' port naming
'dpdk' ports no longer have naming restrictions. Now, instead of
specifying the dpdk port ID as part of the name, the PCI address of the
device must be specified via the 'dpdk-devargs' option. eg.
ovs-vsctl add-port br0 my-port
ovs-vsctl set Interface my-port type=dpdk
options:dpdk-devargs=0000:06:00.3
The user must no longer hotplug attach DPDK ports by issuing the
specific ovs-appctl netdev-dpdk/attach command. The hotplug is now
automatically invoked when a valid PCI address is set in the
dpdk-devargs. The format for ovs-appctl netdev-dpdk/detach command
has changed in that the user now must specify the relevant PCI address
as input instead of the port name.
Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
Co-authored-by: Kevin Traynor <ktraynor@redhat.com>
Acked-by: Stephen Finucane <stephen@that.guru> # docs only
Signed-off-by: Daniele Di Proietto <diproiettod@vmware.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/howto/dpdk.rst | 7 | ||||
| -rw-r--r-- | Documentation/intro/install/dpdk.rst | 9 |
2 files changed, 10 insertions, 6 deletions
diff --git a/Documentation/howto/dpdk.rst b/Documentation/howto/dpdk.rst index 13da54801..1ff672c6a 100644 --- a/Documentation/howto/dpdk.rst +++ b/Documentation/howto/dpdk.rst @@ -312,14 +312,13 @@ In order to attach a port, it has to be bound to DPDK using the Then it can be attached to OVS:: - $ ovs-appctl netdev-dpdk/attach 0000:01:00.0 - -At this point, the user can create a dpdk port using the ``add-port`` command. + $ 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 dpdk0 + $ ovs-appctl netdev-dpdk/detach dpdkx 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 diff --git a/Documentation/intro/install/dpdk.rst b/Documentation/intro/install/dpdk.rst index 10ceabba4..fff0a1a52 100644 --- a/Documentation/intro/install/dpdk.rst +++ b/Documentation/intro/install/dpdk.rst @@ -252,8 +252,13 @@ ports. For example, to create a userspace bridge named ``br0`` and add two ``dpdk`` ports to it, run:: $ ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev - $ ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk - $ ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk + $ ovs-vsctl add-port br0 myportnameone -- set Interface myportnameone \ + type=dpdk options:dpdk-devargs=0000:06:00.0 + $ ovs-vsctl add-port br0 myportnametwo -- set Interface myportnametwo \ + type=dpdk options:dpdk-devargs=0000:06:00.1 + +DPDK devices will not be available for use until a valid dpdk-devargs is +specified. Refer to ovs-vsctl(8) and :doc:`/howto/dpdk` for more details. |