On Tue, Jun 25, 2013 at 4:35 AM, Rajahalme, Jarno (NSN - FI/Espoo) <jarno.rajaha...@nsn.com> wrote: > > On May 7, 2013, at 21:55 , ext Pravin Shelar wrote: > >> On Tue, May 7, 2013 at 11:13 AM, Jarno Rajahalme >> <jarno.rajaha...@nsn.com> wrote: >>> This reduces repeated code and makes it easier to add new UDP tunneling >>> protocols. >>> >> This approach is different from what tunnel upstream patches does. >> Since there is no lisp support in kernel, this patch will make ovs out >> of tree tunneling diverge significantly from upstream ovs tunneling. >> Basically we want to factor out common between upstream vxlan and ovs >> vxlan and keep similar code in out of tree kernel with old kernel >> compatibility code. In future do same with upstream lisp. >> >> I will send out upstream patches soon. > > Is this still in the pipeline for vxlan, or is vxlan code in ovs tree now > stable?
Pravin sent out some patches for upstream OVS VXLAN support last week and hopefully v2 will come tomorrow. Once that's in they will be brought back to OVS, so there's about to be a big change and then hopefully things will calm down a little bit. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
