[ovs-dev] [PATCH RFC v5 0/8] create tunnel devices using rtnetlink interface

[Joe Stringer]

On 16 February 2017 at 14:25, Eric Garver <e at erig.me> wrote:
> This series adds support for the creation of tunnels using the rtnetlink
> interface. This will open the possibility for new features and flags on those
> vports without the need to change vport compatibility code.
>
> Support for STT and LISP have not been added because these are not upstream yet,
> so we don't know how the interface will be like upstream. And there are no
> features in the current drivers right now we could make use of.
>
> Note: This work originally started by Thadeu Lima de Souza Cascardo.

Is there anything in particular about this RFC v5 that you are
requesting comments for, or are you looking for general review?

It looks like travis is failing the userspace build, most likely
because Travis has quite an old kernel. These patches are including
newer linux uapi headers from the user side code. Most likely you will
need to provide linux header backports for a few symbols in the
include/linux/ directory, for example IFLA_VXLAN_LEARNING. The
hardware offloads series that was posted recently is doing a similar
thing for providing linux headers that userspace can build against.
https://travis-ci.org/joestringer/openvswitch/builds/210668063

I ran the system tests on a variety of platforms and they seemed to work fine.