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
<thomasfherb...@entpnt.com> wrote:
This is the linux kernel datapath portion of the 802.1AD patch.
Signed-off-by: Thomas F Herbert <thomasfherb...@entpnt.com>
---
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 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?
--Tom
--
Thomas F. Herbert
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
