From: Neal Cardwell <ncardwell@google.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Bloat] dropbox, bbr and ecn packet capture
Date: Sat, 25 Apr 2020 23:10:11 -0400 [thread overview]
Message-ID: <CADVnQyk7VdaJjP5fov0+nbirgnCpD1b=yUY_wd71bOGzK+dPgQ@mail.gmail.com> (raw)
In-Reply-To: <85F248E2-E1B5-45A6-8E45-EBCA43B82A09@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Sat, Apr 25, 2020 at 8:52 PM Jonathan Morton <chromatix99@gmail.com>
wrote:
> > On 26 Apr, 2020, at 3:36 am, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > I just did a rather large dropbox download. They are well known to be
> > using bbr and experimenting with bbrv2. So I fired off a capture
> > during a big dropbox download...
> >
> > It negotiated ecn, my fq_codel shaper and/or my newly ath10k
> > fq_codel's wifi exerted CE, osx sent back ecn-echo, and the rtt
> > results were lovely. However, there is possibly not a causal
> > relationship here, and if anyone is bored and wants to scetrace,
> > tcptrace or otherwise tear this cap apart, go for it.
>
> Well, the CE response at their end is definitely not Multiplicative
> Decrease. I haven't dug into it more deeply than that. But they're also
> not running AccECN, nor are they "proactively" sending CWR to get a "more
> accurate" CE feedback. I suspect they're running BBRv1 in this one.
Agreed, that looks like BBRv1. I see a few BBRv1 PROBE_RTT phases in there.
Thanks for the trace!
best,
neal
[-- Attachment #2: Type: text/html, Size: 1642 bytes --]
next prev parent reply other threads:[~2020-04-26 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 0:36 [Ecn-sane] " Dave Taht
2020-04-26 0:52 ` [Ecn-sane] [Bloat] " Jonathan Morton
2020-04-26 3:10 ` Neal Cardwell [this message]
[not found] ` <mailman.79.1587870632.24343.bloat@lists.bufferbloat.net>
2020-04-26 23:33 ` Alexey Ivanov
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADVnQyk7VdaJjP5fov0+nbirgnCpD1b=yUY_wd71bOGzK+dPgQ@mail.gmail.com' \
--to=ncardwell@google.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
/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