[ovs-dev] [patch_ports 3/4] ofproto-dpif: Implement patch ports in userspace.

Ben Pfaff blp at nicira.com
Wed Jan 16 23:45:06 UTC 2013


On Tue, Jan 15, 2013 at 01:39:43PM -0800, Ethan Jackson wrote:
> I've folded this incremental in.
> 
> ---
>  FAQ  |   12 +++---------
>  NEWS |    1 +
>  2 files changed, 4 insertions(+), 9 deletions(-)
> 
> diff --git a/FAQ b/FAQ
> index 6d14fc8..b9f655b 100644
> --- a/FAQ
> +++ b/FAQ
> @@ -172,17 +172,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.
> -

How about if we add some additional explanation, just to make it
really explicit.  Also, we can update the list of tunnel types and
drop the list format since now there's only one bullet.  Like this:

A: The kernel module in upstream Linux 3.3 and later does not include
   tunnel virtual ports, that is, interfaces with type "gre",
   "ipsec_gre", "gre64", "ipsec_gre64", "vxlan", or "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 tunnel virtual ports to the upstream
   Linux version of the Open vSwitch kernel module.  For now, if you
   need these features, use the kernel module from the Open vSwitch
   distribution instead of the upstream Linux kernel module.

   The upstream kernel module does not include patch ports, but this
   only matters for Open vSwitch 1.9 and earlier, because Open vSwitch
   1.10 and later implement patch ports without using this kernel
   feature.

Otherwise, thanks for the update.



More information about the dev mailing list