From: Jonathan Morton <chromatix99@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Steinar H. Gunderson" <sgunderson@bigfoot.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:38:18 +0200 [thread overview]
Message-ID: <567310A9-77A4-4AA6-8AED-08EC819DFD8F@gmail.com> (raw)
In-Reply-To: <1480799260.18162.418.camel@edumazet-glaptop3.roam.corp.google.com>
> On 3 Dec, 2016, at 23:07, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
> I do not attend IETF meetings so maybe my words are not exact.
>
> What I meant was that we receive ACKS in bursts, with huge gaps between
> them.
>
> Look at tsval/tsecr, and that all ACKS are received in a 20 usec time
> window, covering data that was sent in a 5 ms window.
Nevertheless, there are no acks obviously *missing*. Decimation would be aggregation of acks such that all but the last (over some interval) is dropped. Here, they are merely delivered in rapid succession.
It could be that the receiver has poor receive-interrupt latency, or that it is aggregating the reverse send path too heavily. The variable spacing within the ack burst (in particular, in both examples the gap between first and second is larger than the rest) favours the former explanation.
- Jonathan Morton
next prev parent reply other threads:[~2016-12-03 21:38 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
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 [this message]
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=567310A9-77A4-4AA6-8AED-08EC819DFD8F@gmail.com \
--to=chromatix99@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=sgunderson@bigfoot.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