On Wednesday, January 07, 2015 01:10:10 PM Thomas F Herbert wrote: > Thanks, > > Some questions are below... > > On 12/31/14 4:16 PM, Pravin Shelar wrote: > > On Tue, Dec 30, 2014 at 7:12 AM, Thomas F Herbert > > <[email protected]> wrote: > >> This is the linux kernel datapath portion of the 802.1AD patch. > >> > >> > >> Signed-off-by: Thomas F Herbert <[email protected]> > >> > >> --- > >> datapath/actions.c | 32 ++++++--- > >> datapath/flow.c | 80 > >> +++++++++++++++++++---- > >> datapath/flow.h | 1 + > >> datapath/flow_netlink.c | 62 ++++++++++++++++-- > >> datapath/linux/compat/include/linux/openvswitch.h | 16 ++--- > >> 5 files changed, 153 insertions(+), 38 deletions(-) > >> > > OVS datapath feature development is moved to netdev mailing list and > > all patches should be developed against net-next tree. Here is > > announcement: > > > > http://openvswitch.org/pipermail/dev/2014-December/049513.html > Flavio, could you please clarify the process between openvswitch > maintained by OVS and the openvswitch in net-next and where the kernel > openvswitch patches are applied first?
I think you meant Pravin, not me. Anyway, there are two kernel modules being maintained at the moment. One resides in the upstream linux git repo and the other is in openvswitch git repo. They are pretty much in sync right now, so you're free to use any of them. However, new features should be developed against upstream linux git repo which for networking stuff is the net-next git tree. The discussions and reviews happen at netdev mailing list. Thus you should post the patches to both ovs dev and netdev mailing lists to pass the review process. When the patches are accepted on net-next, you are supposed to provide equivalent patches for the module in the OVS git repo too taking care to not break compatibility with older kernel versions. > I am working on V6 of the kernel portion of this patch and I need to > incorporate changes that apply to vlan handling in 3.18 kernel from this > patch, "[ovs-dev] [PATCH 0/8 v3] Datapath backports to support 3.18.x, > net, net-next." However I see that patch applied to openvswitch master > here but don't see them in net-next yet? Those patches are to keep the kernel portion maintained in OVS git repo compatible with older and newer kernels. So, they don't make any sense in the upstream net-next repo. fbl _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
