I'm probably the wrong person to give advice on kernel development, since I haven't been involved in it for years. I just know that it's difficult, and not always because of the code.
It's hard to support a protocol in OVS before it's supported in the kernel, since userspace without a kernel implementation is not very useful. On Wed, Jun 01, 2016 at 09:59:12PM +0000, Elzur, Uri wrote: > Hi Ben > > Any guidance you can offer will be appreciated. The process has taken long > time and precious cycles. How can we get to a coordinated Kernel and OvS > approach to avoid the challenges and potentially misaligned advise we got > (per Yi Yang's mail)? > > Thx > > Uri ("Oo-Ree") > C: 949-378-7568 > > > -----Original Message----- > From: Ben Pfaff [mailto:b...@ovn.org] > Sent: Tuesday, May 31, 2016 9:48 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Neutron] support of NSH in networking-SFC > > On Wed, Jun 01, 2016 at 12:08:23AM +0000, Yang, Yi Y wrote: > > Ben, yes, we submitted nsh support patch set last year, but ovs > > community told me we have to push kernel part into Linux kernel tree, > > we're struggling to do this, but something blocked us from doing this. > > It's quite difficult to get patches for a new protocol into the kernel. > You have my sympathy. > > > Recently, ovs did some changes in tunnel protocols which requires the > > packet decapsulated by a tunnel must be a Ethernet packet, but Linux > > kernel (net-next) tree accepted VxLAN-gpe patch set from Redhat guy > > (Jiri Benc) which requires the packet decapsulated by VxLAN-gpe port > > must be L3 packet but not L2 Ethernet packet, this blocked us from > > progressing better. > > > > Simon Horman (Netronome guy) has posted a series of patches to remove > > the mandatory requirement from ovs in order that the packet from a > > tunnel can be any packet, but so far we didn't see they are merged. > > These are slowly working their way through OVS review, but these also have a > prerequisite on kernel patches, so it's not easy to get them in either. > > > I heard ovs community looks forward to getting nsh patches merged, it > > will be great if ovs guys can help progress this. > > I do plan to do my part in review (but much of this is kernel review, which > I'm not really involved in anymore). > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev