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? Jarno > >> Signed-off-by: Jarno Rajahalme <jarno.rajaha...@nsn.com> >> --- >> datapath/tunnel.c | 126 ++++++++++++++++++++++++++++++++++++ >> datapath/tunnel.h | 48 ++++++++++++++ >> datapath/vport-lisp.c | 167 >> ++++-------------------------------------------- >> datapath/vport-vxlan.c | 166 ++++------------------------------------------- >> 4 files changed, 201 insertions(+), 306 deletions(-) >> ... _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
