From: Billy O'Mahony <billy.o.mah...@intel.com>
Unlike system interfaces, DPDK enabled interfaces must have their interface
type explicitly set when used to create bonded ports. Mention this at the
relevant points in the documentation.
Signed-off-by: Billy O'Mahony <billy.o.mah...@intel.com>
---
FAQ.md | 5 +++--
INSTALL.DPDK.md | 8 ++++++++
utilities/ovs-vsctl.8.in | 4 +++-
3 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/FAQ.md b/FAQ.md
index 21d4e7a..9e50571 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -635,8 +635,9 @@ A: More than likely, you've looped your network. Probably,
eth0 and
ovs-vsctl add-br br0
ovs-vsctl add-bond br0 bond0 eth0 eth1
- Bonds have tons of configuration options. Please read the
- documentation on the Port table in ovs-vswitchd.conf.db(5)
+ Bonds have tons of configuration options and the configuration
+ for DPDK enabled interfaces is less straightforward. Please read
+ the documentation on the Port table in ovs-vswitchd.conf.db(5)
for all the details.
- Perhaps you don't actually need eth0 and eth1 to be on the
diff --git a/INSTALL.DPDK.md b/INSTALL.DPDK.md
index 60889d0..871be2b 100644
--- a/INSTALL.DPDK.md
+++ b/INSTALL.DPDK.md
@@ -182,6 +182,14 @@ Using the DPDK with ovs-vswitchd:
polls dpdk device in continuous loop. Therefore CPU utilization
for that thread is always 100%.
+ Note: creating bonds of DPDK interfaces is slightly different to creating
+ bonds of system interfaces. For DPDK, the interface type must be explicitly
+ set, for example:
+
+ ```
+ ovs-vsctl add-bond br0 dpdk0 dpdk1 -- set Interface dpdk0 type=dpdk -- set
Interface dpdk1 type=dpdk
+ ```
+
7. Add test flows
Test flow script across NICs (assuming ovs in /usr/src/ovs):
diff --git a/utilities/ovs-vsctl.8.in b/utilities/ovs-vsctl.8.in
index 0a629f6..785857d 100644
--- a/utilities/ovs-vsctl.8.in
+++ b/utilities/ovs-vsctl.8.in
@@ -282,7 +282,9 @@ is an error. With \fB\-\-may\-exist\fR, this command does
nothing if
.IP "[\fB\-\-fake\-iface\fR] \fBadd\-bond \fIbridge port iface\fR\&...
[\fIcolumn\fR[\fB:\fIkey\fR]\fR=\fIvalue\fR]\&...\fR"
Creates on \fIbridge\fR a new port named \fIport\fR that bonds
together the network devices given as each \fIiface\fR. At least two
-interfaces must be named.
+interfaces must be named. If the interfaces are DPDK enabled then
+the transaction will need to include operations to explicitly set the
+interface type to 'dpdk'.
.IP
Optional arguments set values of column in the Port record created by
the command. The syntax is the same as that for the \fBset\fR command
--
1.7.4.1
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
