Joe, I checked current ovs and net-next kernel, obviously some patches from net-next are selectively backported to ovs, but others are not, I'm not sure what the policy is for a new patch. It will be better that the person who did the patch backports it to ovs at the same time, but nobody did so.
My 802.1ad backport has included all the things l3 patch set depends on, so I think you can give it a go :-) To make sure 802.1ad to work, there is still a userspace work to do, but as Pravin said, this has no business with l3 patch set. -----Original Message----- From: Joe Stringer [mailto:[email protected]] Sent: Tuesday, February 7, 2017 8:34 AM To: Yang, Yi Y <[email protected]> Cc: ovs dev <[email protected]>; Yi-Hung Wei <[email protected]> Subject: Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs On 6 February 2017 at 05:04, Yi Yang <[email protected]> wrote: > This patch set just ports Jiri Benc's L3 8 support patches for layer 3 > encapsulated packets from net-next to current ovs, it also includes Jiri > Benc's 3 userspace patches, Jarno Rajahalme and Pravin Shelar's vlan fix > patches for L3 patchset as well as my 3 patches which enabled vxlangpe in > compat mode and dpdk netdev in both L2 and L3(layer3=true) mode. > > This patchset has been verified on Ubuntu 14.04 x86_64 with Linux kernel > 3.13.0-24-generic and 4.9.7, it also passed "make check" > and "sudo make check-kmod RECHECK=yes" in Fedora 23 with kernel > 4.2.3-300.fc23.x86_64 > > This patch set is based on > https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328492.html > ([PATCH v2 0/4] Backport 802.1ad patches), please merge this one after > merging [PATCH v2 0/4] Backport 802.1ad patches. Thanks for this work! I think that this comprises the majority of the remaining diff between the backport and the upstream tree, though there are still a bunch of other unrelated changes that are still missing. As we discussed earlier, it'd be good to ensure that we don't miss any of the small patches as well; to avoid this, my expectation would be that we can apply backports of all of the missing patches from net-next in the order they were applied to net-next. I believe that Yi-Hung is interested at looking at backporting those other missing patches up until the 802.1ad changes. From there we can review the 802.1ad backport series you have posted, then continue backporting up until the L3 tunnelling backport you've proposed. I'm not really sure how much work is involved in this at the moment, although I think that 802.1ad and L3 tunnelling were the largest features. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
