X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=FAQ;h=4a8a5beecf410a9cc840f86acc6a4dee17820ba1;hb=c9b94429894d34fc84bd0db4f9805b5e59f7e454;hp=cd3241a30a0b96d11f57f2dcdb90c90c5b3a77b9;hpb=1d5aaa61fa8ca68f487e8b578b7aa99a0bbd1f26;p=sliver-openvswitch.git

diff --git a/FAQ b/FAQ
index cd3241a30..4a8a5beec 100644
--- a/FAQ
+++ b/FAQ
@@ -468,6 +468,27 @@ A: Open vSwitch uses different kinds of flows for different purposes:
         regardless of the type.
 
 
+Performance
+-----------
+
+Q: I just upgraded and I see a performance drop.  Why?
+
+A: The OVS kernel datapath may have been updated to a newer version than
+   the OVS userspace components.  Sometimes new versions of OVS kernel
+   module add functionality that is backwards compatible with older
+   userspace components but may cause a drop in performance with them.
+   Especially, if a kernel module from OVS 2.1 or newer is paired with
+   OVS userspace 1.10 or older, there will be a performance drop for
+   TCP traffic.
+
+   Updating the OVS userspace components to the latest released
+   version should fix the performance degradation.
+
+   To get the best possible performance and functionality, it is
+   recommended to pair the same versions of the kernel module and OVS
+   userspace.
+
+
 Configuration Problems
 ----------------------