On Fri, Jul 17, 2015 at 3:58 AM, Thomas Graf <tg...@suug.ch> wrote: > On 07/16/15 at 02:36pm, Pravin Shelar wrote: >> On Thu, Jul 16, 2015 at 7:52 AM, Thomas Graf <tg...@suug.ch> wrote: >> > I'm inclined to change this and use an in-kernel API as well to >> > create the net_device just like VXLAN does in patch 21. >> > >> > Pravin, what do you think? >> >> About the vxlan APIs we also need to direct netlink interface for >> userspace to configure vxlan device. This will allow us to remove >> vxlan compat code from ovs vport-netdev.c in future. > > Do you mean creating the tunnel devices from user space? This would > break existing users of the OVS Netlink interface. How do you want > to prevent that? To handle old interface there is compat code in netdev-vport in patch 22.
OVS userspace should be able to create any type of tunneling device and then add it as netdev type vport. so that OVS has two types of vport i.e. netdev and internal, rather than vport for each type of tunnel. This way we can keep compat code simple. All enhancements can be directly done to new interface. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
