From: David Lang <david@lang.hm>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net, "Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [Bloat] Bufferbloat on 4G Connexion
Date: Wed, 23 Oct 2019 10:52:26 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1910231047010.4488@qynat-yncgbc> (raw)
In-Reply-To: <0876C235-C6D3-42B0-9D93-114DB75D4204@gmail.com>
On Wed, 23 Oct 2019, Rich Brown wrote:
> I only have a 30,000 foot understanding of this work, but it seems the use of AQL (Airtime Queue Limit) maps better onto the vagaries of 4G/5G radio transmissions than BQL. Specifically, having a measurement of the actual time it takes to transmit a packet might give additional information about the current link speed, with the potential for adjusting the codel target, etc.
The key thing in both BQL and AQL is that instead of treating all packets the
same, you account for how long it will take to transmit them.
In Wifi, your transmission rate can vary by a factor of 1000x (1Mb to over 1Gb
per second), so just counting bytes as BQL does is no longer good enough.
how much does the actual over-the-air transmission rate vary in 4G? I'd bet that
it varies less than wifi does because wifi must retain compatibility with the
earliest equipment while 4G no longer supports 2G protocols.
is it just a matter of each phone getting a smaller slice of the airtime when
things get busy? or does the actual data rate for that slice of airtime
decrease as well?
David Lang
next prev parent reply other threads:[~2019-10-23 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.865.1571824497.1240.bloat@lists.bufferbloat.net>
2019-10-23 11:56 ` Rich Brown
2019-10-23 12:27 ` Toke Høiland-Jørgensen
2019-10-24 7:26 ` Luca Muscariello
2019-10-24 9:34 ` Toke Høiland-Jørgensen
2019-10-24 12:55 ` Luca Muscariello
2019-10-24 14:02 ` Toke Høiland-Jørgensen
2019-10-23 17:52 ` David Lang [this message]
2019-10-24 11:51 ` erik.taraldsen
2019-10-24 12:14 ` Toke Høiland-Jørgensen
2019-10-24 12:14 ` Jonathan Morton
2019-10-11 14:56 Guillaume ROBIER
2019-10-22 21:02 ` Jonathan Morton
2019-10-23 7:28 ` erik.taraldsen
2019-10-23 8:24 ` David Lang
2019-10-23 8:37 ` Sebastian Moeller
2019-10-23 9:54 ` Jonathan Morton
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=nycvar.QRO.7.76.6.1910231047010.4488@qynat-yncgbc \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
--cc=toke@redhat.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