, Darrell Ball wrote:
>
> On 4/3/17, 5:27 AM, "ovs-dev-boun...@openvswitch.org on behalf of Przemyslaw
Lal" wrote:
>
> In current implementation port_id is used as an ifindex for all
netdev-dpdk
> interfaces.
>
>
lution to these issues is to calculate a hash of interface's name
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
lution to these issues is to calculate a hash of interface's name
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
findex values by the same virtual interfaces and maximum ifindex value.
Signed-off-by: Przemyslaw Lal
---
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/net
re-using ifindex values by the same virtual interfaces.
Signed-off-by: Przemyslaw Lal
---
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 ch
lution to these issues is to calculate a hash of interface's name
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
ifi
