[ovs-dev] [PATCH net-next v12 0/9] openvswitch: support for layer 3 encapsulated packets
pshelar at ovn.org
Wed Oct 19 05:11:21 UTC 2016
On Mon, Oct 17, 2016 at 6:02 AM, Jiri Benc <jbenc at redhat.com> wrote:
> At the core of this patch set is removing the assumption in Open vSwitch
> datapath that all packets have Ethernet header. Support for layer 3 GRE
> tunnels is also added by this patchset.
> The implementation relies on the presence of pop_eth and push_eth actions
> in datapath flows to facilitate adding and removing Ethernet headers as
> appropriate. The construction of such flows is left up to user-space.
> This series is based on work by Simon Horman, Lorand Jakab, Thomas Morin and
> others. I kept Lorand's and Simon's s-o-b in the patches that are derived
> from v11 to record their authorship of parts of the code. Please let me know
> if you disagree with this.
> v12 differs from v11 a lot. The main changes are:
> * The patches were restructured and split differently for easier review.
> * They were rebased and adjusted to the current net-next. Especially MPLS
> handling is different (and easier) thanks to the recent MPLS GSO rework.
> * Several bugs were discovered and fixed. The most notable is fragment
> handling: header adjustment for ARPHRD_NONE devices on tx needs to be done
> after refragmentation, not before it. This required significant changes in
> the patchset. Another one is stricter checking of attributes (match on L2
> vs. L3 packet) at the kernel level.
> * Instead of is_layer3 bool, a mac_proto field is used. See patch 2. This is
> a matter of taste and alternate approaches are offered in patch 2
> There is no change to uAPI since v11. The previously posted patchset for
> Open vSwitch user space works with this submission unmodified.
I have not finished the review yet, but most of patches looks good to
me. Can you send userspace patches against latest master so that I can
try the patches with tunnel setup?
More information about the dev