Sorry for the late reply. I missed this sub-thread somehow. On Thu, Jul 14, 2016 at 09:38:09AM +0800, Xiao Liang wrote: > As far as I know, Eric and Tom are working on the kernel patch set and > would submit a new version to net-next. Kernel patches usually go to > netdev first and then backported to OVS tree. Meanwhile, this
Yes. I'm currently resuming Tom's work. I'm hoping to post a new set of kernel patches to netdev in the coming weeks. Stay tuned! > userspace patch works with current kernel module, with a limitation > that inner VLAN header can not be matched, which should only impact > the egress cvlan check. It would be nice if you could help try and > review these patches. > Regarding neutron part, Bo is working on it, and we are looking for a > way to get OVS capabilities. Do you think it's better submit for > discuss now or wait for the OVS part to be ready? > > Thanks, > Xiao > > On Thu, Jul 14, 2016 at 2:35 AM, Carl Baldwin <c...@ecbaldwin.net> wrote: > > On Sat, Jun 25, 2016 at 4:13 AM, Xiao Liang <shaw.l...@gmail.com> wrote: > >> > >> Hi, > >> > >> I'm looking for QinQ support in OVS for some time. And found patches[1-3] > >> by Thomas, and Gayathri. What I want is to use QinQ tunneling in neutron > >> networking, which needs vlan_mode configuration of ports (as in Gayathri's > >> patch) as well as openflow VLAN manipulating action support (as in Thomas's > >> patch). Unfortunately, these patches are not compatible, so I made this > >> patch. > >> It's based on Thomas's kernel patch and reference the idea from Gayathri, > >> and is (in my tests) backward compatible. Although the kernel patch not > >> merged yet, I believe the nlmsg will not change. > > > > > > I haven't seen much discussion on the kernel patches that you reference > > since they were proposed in November. I'm unfamiliar with the process for > > landing changes like this which span the linux and ovs repositories. Is > > there effort being made elsewhere to get these to land? Where might I look > > to follow that effort? Is there anything I can do to help with the process? > > > > Carl > > > >> References: > >> [1] openvswitch: 802.1ad uapi changes, Thomas F Herbert, > >> https://patchwork.ozlabs.org/patch/540673/ > >> Check for vlan ethernet types for 8021.q or 802.1ad, > >> https://patchwork.ozlabs.org/patch/540668/ > >> openvswitch: 802.1AD: Flow handling, actions, vlan parsing and netlink > >> attributes, https://patchwork.ozlabs.org/patch/540671/ > >> [2] Add 802.1ad (qinq) support, Thomas F Herbert, > >> http://openvswitch.org/pipermail/dev/2015-October/060874.html > >> [3] 802.1ad support in OVS & OVS-DPDK, Gayathri Manepalli, > >> http://openvswitch.org/pipermail/dev/2016-February/066265.html > >> > > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev