From: Dave Taht <dave.taht@gmail.com>
To: Prateesh Goyal <g.pratish@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>,
Hari Balakrishnan <hari@csail.mit.edu>,
Mohammad Alizadeh <alizadeh@csail.mit.edu>
Subject: Re: [Ecn-sane] abc congestion control on time varying wireless links
Date: Wed, 11 Dec 2019 11:54:05 -0800 [thread overview]
Message-ID: <CAA93jw7cHxz_adN4ezBEvtWtiduFqghSn335Cp+RAtyEBWt5sw@mail.gmail.com> (raw)
In-Reply-To: <CAOqqZ1b3w=cgBYPoEhqNkMWVNRq1iEbA17xaoi28vwsg_rURFA@mail.gmail.com>
On Wed, Dec 11, 2019 at 11:19 AM Prateesh Goyal <g.pratish@gmail.com> wrote:
>
> Adding Hari, Mohammad
>
> On Wed, Dec 11, 2019 at 2:17 PM Dave Taht <dave.taht@gmail.com> wrote:
>>
>> https://arxiv.org/pdf/1905.03429.pdf
>>
>> the principal item of interest is section 3.1.2 where the accelerate
>> and brake concepts and math are described.
What we have now is a string of conflicts of interest over the values
of the ecn bits, in part based
on the characteristics of the underlying link technologies.
The DC folk want a multibit more immediate signal, for which L4S is
kind of targetted, (and SCE also
applies). I haven't seen any data on how well dctcp or SCE -style can
work on wildly RTT varying links as yet, although it's been pitched at
the LTE direction, not at wifi.
The abc concept hasn't been tried in a DC-like environment, and while
it shows some good results for both the LTE and wifi simulations, was
not compared against the fq_codel based solution currently in linux
wifi, nor against the minstrel rate controller.
I have plenty of data on how fq_codel + RFC3168 ecn currently works on
wifi, I like to think it's pretty good, but it's still pretty slow to
respond with just RFC3168 or drop.
this is yet another one of those cases where unified sets of
benchmarks would help.
And then there's, like, the actual deployment on actual devices... I
just did a string of benchmarks, tethered to my new moto 6e phone. You
saturate the download, and nearly ALL other traffic (icmp and udp) in
the upstream direction, gets starved out.
I just did a string of benchmarks on my new LTE
>>
>> --
>> Make Music, Not War
>>
>> Dave Täht
>> CTO, TekLibre, LLC
>> http://www.teklibre.com
>> Tel: 1-831-435-0729
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2019-12-11 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 19:17 Dave Taht
2019-12-11 19:19 ` Prateesh Goyal
2019-12-11 19:54 ` Dave Taht [this message]
2019-12-11 20:10 ` Dave Taht
2019-12-11 20:12 ` [Ecn-sane] [Bloat] " Jonathan Morton
2019-12-12 21:31 ` Dave Taht
2019-12-11 21:18 ` [Ecn-sane] " David P. Reed
2019-12-11 21:30 ` David P. Reed
2019-12-18 19:43 ` [Ecn-sane] [Bloat] " Dave Taht
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=CAA93jw7cHxz_adN4ezBEvtWtiduFqghSn335Cp+RAtyEBWt5sw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=alizadeh@csail.mit.edu \
--cc=bloat@lists.bufferbloat.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=g.pratish@gmail.com \
--cc=hari@csail.mit.edu \
/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