[ovs-dev] [PATCH 0/6] create tunnel devices using rtnetlink interface

Thadeu Lima de Souza Cascardo cascardo at redhat.com
Thu May 26 20:34:57 UTC 2016


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.

One thing that may be seen as a regression is the MTU of those devices. It won't
be IP_MAX_MTU as in latest upstream, but supporting older kernels restrict us to
use 1500 for VXLAN and GENEVE.

Thadeu Lima de Souza Cascardo (6):
  route-table: if device is not there, route is still parseable
  netdev: get device type from vport prefix if not found
  dpif-netlink: break 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 | 529 ++++++++++++++++++++++++++++++++++++++++++++++++-----
 lib/netdev.c       |  19 ++
 lib/route-table.c  |   6 +-
 3 files changed, 503 insertions(+), 51 deletions(-)

-- 
2.5.5




More information about the dev mailing list