On Tue, Dec 06, 2016 at 03:51:03PM +0100, Jiri Benc wrote: > On Tue, 6 Dec 2016 07:17:20 +0000, Yang, Yi Y wrote: > > So my advice about this is we can push patch [2] to Linux net-next > > first, then apply patch series > > https://mail.openvswitch.org/pipermail/ovs-dev/2016-June/316879.html > > from Cascardo and apply [1], that can cover all the cases Pravin > > mentioned. > > There's no reason to add this to the genetlink interface when we're > going to switch to rtnetlink for tunnel configuration. > But ovs userspace use genetlink to create vxlan tunnel port when we build ovs to use its own compat modules, this is case 3 Pravin, how do you think we can handle this?
Now the dilemma is we can't create vxlangpe port although it has been in ovs, I know it is ok if we use upstream tunnel code, but in many cases, Linux distribution didn't include recent kernels, we have to use ovs' compat modules, Pravin's comments also addressed this. So anybody will change current genetlink in ovs to rtnetlink? I will try to change it if nobody will fix it. Another issue, I think ovs will send rtnetlink message to kernel, right? Can ovs handle rtnetlink message if we use ovs compat modules instead of upstream kernel modules? _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
