Hi Ben,

thank you very much, now the FAQ explanation is definitely clear.

--
Konstantin

On 07/12/2012 07:08 PM, Ben Pfaff wrote:
The previous text was ambiguous.

Reported-by: Konstantin Khorenko<[email protected]>
CC: Jesse Gross<[email protected]>
Signed-off-by: Ben Pfaff<[email protected]>
---
  AUTHORS |    1 +
  FAQ     |   16 ++++++++++------
  2 files changed, 11 insertions(+), 6 deletions(-)

diff --git a/AUTHORS b/AUTHORS
index 1ed820c..2c1a48c 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -127,6 +127,7 @@ John Galgay             [email protected]
  Kevin Mancuso           [email protected]
  Kirill Kabardin
  Koichi Yagishita        [email protected]
+Konstantin Khorenko     [email protected]
  Krishna Miriyala        [email protected]
  Luca Falavigna          [email protected]
  Luiz Henrique Ozaki     [email protected]
diff --git a/FAQ b/FAQ
index 4ad8c43..91f4007 100644
--- a/FAQ
+++ b/FAQ
@@ -143,12 +143,11 @@ A: The kernel module in upstream Linux 3.3 and later does 
not include
           kernel module from the Open vSwitch distribution instead of the
           upstream Linux kernel module.

-       - Tunnel and patch virtual ports, that is, interfaces with type
-         "gre", "ipsec_gre", "capwap", or "patch".  It is possible to
-         create tunnels in Linux and attach them to Open vSwitch as
-         system devices.  However, they cannot be dynamically created
-         through the OVSDB protocol or set the tunnel ids as a flow
-         action.
+       - Tunnel virtual ports, that is, interfaces with type "gre",
+         "ipsec_gre", "capwap".  It is possible to create tunnels in
+         Linux and attach them to Open vSwitch as system devices.
+         However, they cannot be dynamically created through the OVSDB
+         protocol or set the tunnel ids as a flow action.

           Work is in progress in adding these features to the upstream
           Linux version of the Open vSwitch kernel module.  For now, if
@@ -156,6 +155,11 @@ A: The kernel module in upstream Linux 3.3 and later does 
not include
           vSwitch distribution instead of the upstream Linux kernel
           module.

+       - Patch virtual ports, that is, interfaces with type "patch".
+         You can use Linux "veth" devices as a substitute.
+
+         We don't have any plans to add patch ports upstream.
+
  Q: What features are not available when using the userspace datapath?

  A: Tunnel and patch virtual ports are not supported, as described in the
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev

Reply via email to