[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZ+APJZsECj3D_rFFPw82k3u6jgkbGzYnwaVmTUcrH5xiQ@mail.gmail.com>
Date: Thu, 24 Jul 2014 09:58:34 +0300
From: Or Gerlitz <or.gerlitz@...il.com>
To: Andy Zhou <azhou@...ira.com>, Tom Herbert <therbert@...gle.com>
Cc: David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [net-next 00/10] Add Geneve
On Tue, Jul 22, 2014 at 1:19 PM, Andy Zhou <azhou@...ira.com> wrote:
> Following patches adds initial support for Geneve tunnel protocol
Just to make this a bit more clear, would it be correct to say that
the logical ordering here is as follows:
> 1. Add common UDP tunnel code into UDP tunnel support function
> 2. Refactor vxlan driver to make use of the UDP tunnel support
> 3. Add Geneve driver.
implemented by patches 1-5 below)
> Andy Zhou (5):
> net: Rename ndo_add_vxlan_port to ndo_add_udp_tunnel_port.
> udp: Expand UDP tunnel common APIs
> vxlan: Remove vxlan_get_rx_port()
> net: Refactor vxlan driver to make use of common UDP tunnel functions
> net: Add Geneve tunneling protocol driver
and on top of that
> 4. Refactor Openvswitch in preparation for #5
> 5. Add Geneve support to Openvswitch.
implemented by patches 6-10 (below)
> Jesse Gross (5):
> openvswitch: Eliminate memset() from flow_extract.
> openvswitch: Add support for matching on OAM packets.
> openvswitch: Wrap struct ovs_key_ipv4_tunnel in a new structure.
> openvswitch: Factor out allocation and verification of actions.
> openvswitch: Add support for Geneve tunneling.
I understand the wish to eventually have something that goes beyond
refactoring of
the vxlan and tunneling code plus Geneve basics. However, isn't the
1st part of the series
(patches 1-5) have something is common to Tom's GUE work, which is
currently under review
too? I think we need first see how the basic elements from your series
go along together with GUE.
Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists