With verbose logging, i see revalidator reporting less packets with i40e
in comparison with better scenario as in ixgbe.
i40e:
2017-07-31T06:21:26.510Z|00759|dpif(revalidator50)|DBG|netdev@ovs-netdev:
flow_dump ufid:e72fca54-e8c3-4066-a474-10eb8ca8e152 <empty>, packets:27,
bytes:38018, used:0.003s, flags:P.
ixgbe:
2017-07-31T05:45:17.999Z|00969|dpif(revalidator49)|DBG|netdev@ovs-netdev:
flow_dump ufid:98225e69-e180-4880-aa85-0be2eff19251 <empty>,
packets:1568, bytes:2371092, used:0.000s, flags:P.
This is the case with tcp. Less count alarms possible delay of tcp
packets reaching network
stack through bonding port, hence tcp slows down overall. I don't see
any difference
with udp traffic between these cards though.
Any pointer within ovs datapath to chase possible reasons for this delay ?
To note, I also tried disabling tcp seg offload within NICs, but no
difference in
problem.
Thanks,
Gowrishankar
On Thursday 27 July 2017 03:41 PM, gowrishankar muthukrishnan wrote:
Hi,
I am using XL710 NIC (2 ports) as part of OVS bonding port in
active-backup mode
in x86_64 servers. Setup is pretty simple. Two machines each with
XL710 NIC
connected each other back-to-back on these ports. Bonding is setup
through OVS
active-backup mode. After bonding port is created, I assign an IP
address on
bridge and run iperf for TCP perf comparison.
iperf (with default params) between bonding ports shows very less
throughput of
around 1 Mbps where as in same server, when I use 82599 (ixgbe) I find
better
throughput of around 20 Mbps. I tried with dpdk poll mode driver as
well. It helps
ixgbe to get near 250 Mbps but, same poor performance I get for i40e.
Has anyone observed this reduced throughput (with or without dpdk) in
XL710
while in OVS active-backup bonding ?. Any pointer to find hot spot
causing
trouble (I am trying perf for the moment).
OVS version of 2.6 as well as 2.7 tried (along with dpdk 16.11.1).
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
