On 04/04/2017 06:14, Darrell Ball wrote:
>
> On 4/3/17, 5:27 AM, "ovs-dev-boun...@openvswitch.org on behalf of Przemyslaw
Lal" <ovs-dev-boun...@openvswitch.org on behalf of przemyslawx@intel.com> wrote:
>
>
.
Signed-off-by: Przemyslaw Lal <przemyslawx@intel.com>
---
lib/netdev-dpdk.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c
index ddc651b..687b0a5 100644
--- a/lib/netdev-dpdk.c
+++ b/lib/netdev-dpdk.c
@@ -2215,7 +2
and use calculated value as an ifindex. This way interfaces keep their
ifindexes during OVS-DPDK restarts, ports re-initialization events, etc., show
up in sFlow collectors and meet RFC2863 specification regarding re-using
ifindex values by the same virtual interfaces.
Signed-off-by: Przemyslaw Lal
and use calculated value as an ifindex. This way interfaces keep their
ifindexes during OVS-DPDK restarts, ports re-initialization events, etc., show
up in sFlow collectors and meet RFC2863 specification regarding re-using
ifindex values by the same virtual interfaces.
Signed-off-by: Przemyslaw Lal
-by: Przemyslaw Lal <przemyslawx@intel.com>
---
Thanks for the patch.
I'm not the most experienced with sflow but after looking into it its clear the
need for a change to ifindex is required for DPDK devices.
lib/netdev-dpdk.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff
and use calculated value as an ifindex. This way interfaces keep their
ifindexes during OVS-DPDK restarts, ports re-initialization events, etc., show
up in sFlow collectors and meet RFC2863 specification regarding re-using
ifindex values by the same virtual interfaces.
Signed-off-by: Przemyslaw
