On Sat, 2016-12-03 at 23:13 +0100, Steinar H. Gunderson wrote: > On Sat, Dec 03, 2016 at 01:50:37PM -0800, Eric Dumazet wrote: > >> Note, the tcpdump is done at the receiver. I don't know if this changes the > >> analysis. > > If you have access to the receiver, I would be interested to know > > NIC/driver used there ? > > root@blackhole:~# lspci | grep Ethernet > 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network > Connection > 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network > Connection > > root@blackhole:~# lspci -n | grep 01:00.0 > 01:00.0 0200: 8086:10d3 > > root@blackhole:~# ls -l /sys/class/net/eth0/device/driver > lrwxrwxrwx 1 root root 0 des. 3 23:17 /sys/class/net/eth0/device/driver -> > ../../../../bus/pci/drivers/e1000e > > root@blackhole:~# uname -a > Linux blackhole 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) > x86_64 GNU/Linux > > Do note, both eth0 and eth1 are a bridge, although only one of the cards are > actually connected to anything (it's just so the remote hands can connect to > any port and things will come up fine).
Perfect. Note that starting from linux-4.4, e1000e gets gro_flush_timeout that would help this precise workload https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=32b3e08fff60494cd1d281a39b51583edfd2b18f Maybe you can redo the experiment in ~5 years when distro catches up ;) Thanks. _______________________________________________ aqm mailing list aqm@ietf.org https://www.ietf.org/mailman/listinfo/aqm