If rtnetlink user space patches aren't merged, I don't think you can use in-kernel data path correctly, yes there are some work to do, but that has to been done after Eric Garver's rtnetlink user space patches are merged. Maybe you can try RFC patches Eric Garver posted https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327749.html,
-----Original Message----- From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev-boun...@openvswitch.org] On Behalf Of Valentine Sinitsyn Sent: Thursday, February 9, 2017 3:58 PM To: ovs-dev@openvswitch.org Subject: Re: [ovs-dev] [PATCH v3 00/16] port Jiri Benc's L3 patchset to ovs Hi all, This L3 patchset looks similar to what we did internally with OVS 2.6 to add support for IPv6 tunnels. Could you please confirm that ovs-dpctl reports correct statistics with this patchset when one uses in-kernel Linux datapath? We had some issues with this (the counters were always zero). Largely, this was because userspace code (I refer to the tools and the daemon, not DPDK datapath here) assumes a plugged network interface is always L2, and I don't see this patch touching these files. Thanks for your co-operation. Best regards, Valentine Sinitsyn _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
