Hi, Cascardo Do you still have plan to continue this? Now VxLAN-gpe code has been in ovs, but we can't create VxLAN-gpe port without your patches, what issues blocked them?
-----Original Message----- From: dev [mailto:[email protected]] On Behalf Of Thadeu Lima de Souza Cascardo Sent: Wednesday, June 22, 2016 11:48 PM To: [email protected] Subject: [ovs-dev] [PATCH v3 0/5] create tunnel devices using rtnetlink interface 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. v2: We are able to set the MTU to UINT16_MAX since it is not restricted by the driver during newlink. v3: Prefer to get type from vport before checking if device is opened. Also, disable IFLA_VXLAN_LEARNING as it's not enabled on compat vports as well. Thadeu Lima de Souza Cascardo (5): netdev: get device type from vport prefix if it uses one dpif-netlink: break out code to add compat and non-compat vports dpif-netlink: add VXLAN creation support dpif-netlink: add GRE creation support dpif-netlink: add GENEVE creation support lib/dpif-netlink.c | 527 ++++++++++++++++++++++++++++++++++++++++++++++++----- lib/netdev.c | 26 ++- 2 files changed, 500 insertions(+), 53 deletions(-) -- 2.7.4 _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
