On Tue, 29 Sep 2015 20:05:00 -0700, Jesse Gross wrote: > This appears to me to be a bug in the existing code. > ovs_tunnel_get_egress_info() as a general mechanism is still in use > and should work with both the old and new configuration methods.
It's currently used only from the compat layer (the API that the user space that is unaware of lwtunnels use). I don't understand what it would be good for with lwtunnel based tunnels. The metadata_dst is created in the validate_and_copy_set_tun function (net/openvswitch/flow_netlink.c) and used to specify egress encapsulation metadata. The ovs_tunnel_get_egress_info function is not needed. > However, I agree that it doesn't look like it will work currently with > tunnel devices. I think we need to fix this rather than making it more > broken. I'm not making it more broken. We currently (i.e. right now, in the current net.git) have two APIs for tunnel specification in the ovs kernel datapath: the old one, which is translated by the compat layer to create a net_device, and the lwtunnel one, which requires user space to create a (metadata) tunnel net_device and add it to the datapath. I'm simply not adding more code to the first, legacy interface, which seems to be the correct thing to do. Jiri -- Jiri Benc -- 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
