From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Neal Cardwell <ncardwell@google.com>,
"aqm@ietf.org" <aqm@ietf.org>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] TCP BBR paper is now generally available
Date: Sat, 3 Dec 2016 23:13:38 +0100 [thread overview]
Message-ID: <20161203221338.GC38041@sesse.net> (raw)
In-Reply-To: <1480801837.18162.419.camel@edumazet-glaptop3.roam.corp.google.com>
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).
/* Steinar */
--
Homepage: https://www.sesse.net/
next prev parent reply other threads:[~2016-12-03 22:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 15:52 Dave Taht
2016-12-02 19:15 ` Aaron Wood
2016-12-02 20:32 ` Jonathan Morton
2016-12-02 22:22 ` Neal Cardwell
2016-12-02 22:40 ` Steinar H. Gunderson
2016-12-02 23:31 ` Eric Dumazet
2016-12-03 13:03 ` Neal Cardwell
2016-12-03 19:13 ` Steinar H. Gunderson
2016-12-03 20:20 ` Eric Dumazet
2016-12-03 20:26 ` Jonathan Morton
2016-12-03 21:07 ` Eric Dumazet
2016-12-03 21:34 ` Steinar H. Gunderson
2016-12-03 21:50 ` Eric Dumazet
2016-12-03 22:13 ` Steinar H. Gunderson [this message]
2016-12-03 22:55 ` Eric Dumazet
2016-12-03 23:02 ` Eric Dumazet
2016-12-03 23:09 ` Eric Dumazet
2016-12-03 23:03 ` Steinar H. Gunderson
2016-12-03 23:15 ` Eric Dumazet
2016-12-03 23:24 ` Eric Dumazet
2016-12-04 3:18 ` Neal Cardwell
2016-12-04 8:44 ` Steinar H. Gunderson
2016-12-04 17:13 ` Eric Dumazet
2016-12-04 17:38 ` Steinar H. Gunderson
2016-12-06 17:20 ` Steinar H. Gunderson
2016-12-06 21:31 ` Neal Cardwell
2016-12-03 21:38 ` Jonathan Morton
2016-12-03 21:33 ` Steinar H. Gunderson
2016-12-07 16:28 ` Alan Jenkins
2016-12-07 16:47 ` Steinar H. Gunderson
2016-12-07 17:03 ` Alan Jenkins
2016-12-08 8:24 ` Mikael Abrahamsson
2016-12-08 13:22 ` Dave Täht
2016-12-08 14:01 ` Mikael Abrahamsson
2016-12-08 21:29 ` Neal Cardwell
2016-12-08 22:31 ` Yuchung Cheng
2016-12-09 14:52 ` Klatsky, Carl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161203221338.GC38041@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox