From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Daniel Sterling <sterling.daniel@gmail.com>,
Luca Muscariello <muscariello@ieee.org>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Carlo Augusto Grazia <carloaugusto.grazia@unimore.it>,
bloat <bloat@lists.bufferbloat.net>,
jamshid@whatsapp.com
Subject: Re: [Make-wifi-fast] [Bloat] the future belongs to pacing
Date: Mon, 06 Jul 2020 19:01:33 +0200 [thread overview]
Message-ID: <87o8oslgr6.fsf@toke.dk> (raw)
In-Reply-To: <CAJZMiueC9JdLUx1Py-wiZHnveWScB+GEBN9P7ie70HC=M2i1Aw@mail.gmail.com>
Daniel Sterling <sterling.daniel@gmail.com> writes:
> On Mon, Jul 6, 2020 at 10:09 AM Luca Muscariello <muscariello@ieee.org> wrote:
>> If BBR can fix that by having a unique model for all these cases that would make deprecation, as intended in the paper,
>> likely to happen.
>
> Interesting! Thank you all for helping a layperson like me understand.
>
> Obviously getting CC / latency control "correct" under wifi is a
> difficult problem.
>
> I am wondering if you (the experts) have confidence we can solve it --
> that is, can end-users eventually see low latency by default with
> standard gear?
>
> Or are shared transmission mediums like wifi doomed to require large
> buffers for throughput, which means low latency can't be something we
> can have "out of the box" -- ? Is sacrificing throughput for latency
> required for "always low" latency on wifi?
To a certain extent, yes. However, this is orthogonal to the congestion
control being used: WiFi gets its high throughput due to large
aggregates (i.e., 802.11ac significantly increases the maximum allowed
aggregation size compared to 802.11n). Because there's a fixed overhead
for each transmission, the only way you can achieve the maximum
theoretical throughput is by filling the aggregates, and if you do that
while there are a lot of users contending for the medium, you will end
up hurting latency.
So really, the right thing to do in a busy network is to lower the
maximum aggregate size: if you have 20 stations waiting to transmit and
each only transmits for 1ms each instead of the maximum 4ms, you only
add 20ms of delay while waiting for the other stations, instead of 80ms
(best-case, not counting any backoff from collisions, queueing delay,
etc).
-Toke
next prev parent reply other threads:[~2020-07-06 17:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 19:53 [Make-wifi-fast] IEEE 802.11n/ac Wireless Network Efficiency under different TCP Congestion Controls Dave Taht
2019-12-13 21:05 ` Carlo Augusto Grazia
2019-12-13 21:25 ` [Make-wifi-fast] the future belongs to pacing Dave Taht
2020-07-04 17:29 ` [Bloat] " Matt Mathis
[not found] ` <mailman.763.1593883755.24343.bloat@lists.bufferbloat.net>
2020-07-04 17:52 ` [Make-wifi-fast] " Daniel Sterling
2020-07-04 18:02 ` Jonathan Morton
2020-07-04 18:29 ` Sebastian Moeller
2020-07-05 6:10 ` Matt Mathis
2020-07-05 12:01 ` [Make-wifi-fast] " Sebastian Moeller
2020-07-05 17:07 ` Matt Mathis
2020-07-05 17:29 ` [Make-wifi-fast] " Sebastian Moeller
2020-07-05 17:43 ` Michael Richardson
2020-07-05 18:09 ` Stephen Hemminger
2020-07-05 18:13 ` Jonathan Morton
2020-07-05 23:06 ` Matt Mathis
2020-07-06 14:08 ` [Make-wifi-fast] " Luca Muscariello
2020-07-06 14:14 ` [Make-wifi-fast] [Bloat] " Daniel Sterling
2020-07-06 17:01 ` Toke Høiland-Jørgensen [this message]
2019-12-13 21:09 ` [Make-wifi-fast] IEEE 802.11n/ac Wireless Network Efficiency under different TCP Congestion Controls Holland, Jake
2019-12-13 21:18 ` Carlo Augusto Grazia
2019-12-13 23:06 ` 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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8oslgr6.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--cc=carloaugusto.grazia@unimore.it \
--cc=jamshid@whatsapp.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=muscariello@ieee.org \
--cc=sterling.daniel@gmail.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