diff options
| author | Ciara Loftus <ciara.loftus@intel.com> | 2017-01-05 10:42:10 +0000 |
|---|---|---|
| committer | Daniele Di Proietto <diproiettod@vmware.com> | 2017-01-05 20:10:19 -0800 |
| commit | 69876ed78611844d6db4b6b62c9a229f185e3fec (patch) | |
| tree | 1259c475e34ee541d4c48ab73592d0e9197ccef3 /Documentation | |
| parent | 55e075e65ef9ecbd70e5e0fada2704c3d73724d8 (diff) | |
| download | openvswitch-69876ed78611844d6db4b6b62c9a229f185e3fec.tar.gz | |
netdev-dpdk: Add support for virtual DPDK PMDs (vdevs)
Prior to this commit, the 'dpdk' port type could only be used for
physical DPDK devices. Now, virtual devices (or 'vdevs') are supported.
'vdev' devices are those which use virtual DPDK Poll Mode Drivers eg.
null, pcap. To add a DPDK vdev, a valid 'dpdk-devargs' must be set for
the given dpdk port. The format expected is 'eth_<driver_name><x>' where
'x' is a number between 0 and RTE_MAX_ETHPORTS -1.
For example to add a port that uses the 'null' DPDK PMD driver:
ovs-vsctl set Interface null0 options:dpdk-devargs=eth_null0
Not all DPDK vdevs have been verified to work at this point in time.
Signed-off-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>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/howto/dpdk.rst | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/Documentation/howto/dpdk.rst b/Documentation/howto/dpdk.rst index 1ff672c6a..fbb4b5361 100644 --- a/Documentation/howto/dpdk.rst +++ b/Documentation/howto/dpdk.rst @@ -324,6 +324,35 @@ 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 <http://dpdk.org/doc/guides/prog_guide/port_hotplug_framework.html#hotplug>`__. +.. _vdev-support: + +Vdev Support +------------ + +DPDK provides drivers for both physical and virtual devices. Physical DPDK +devices are added to OVS by specifying a valid PCI address in 'dpdk-devargs'. +Virtual DPDK devices which do not have PCI addresses can be added using a +different format for 'dpdk-devargs'. + +Typically, the format expected is 'eth_<driver_name><x>' where 'x' is a +number between 0 and RTE_MAX_ETHPORTS -1 (31). + +For example to add a dpdk port that uses the 'null' DPDK PMD driver:: + + $ ovs-vsctl add-port br0 null0 -- set Interface null0 type=dpdk \ + options:dpdk-devargs=eth_null0 + +Similarly, to add a dpdk port that uses the 'af_packet' DPDK PMD driver:: + + $ ovs-vsctl add-port br0 myeth0 -- set Interface myeth0 type=dpdk \ + options:dpdk-devargs=eth_af_packet0,iface=eth0 + +More information on the different types of virtual DPDK PMDs can be found in +the `DPDK documentation +<http://dpdk.org/doc/guides/nics/overview.html>`__. + +Note: Not all DPDK virtual PMD drivers have been tested and verified to work. + .. _dpdk-ovs-in-guest: OVS with DPDK Inside VMs |