From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: erik.taraldsen@telenor.com, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat on 4G Connexion
Date: Thu, 24 Oct 2019 14:14:09 +0200 [thread overview]
Message-ID: <87k18ul4ry.fsf@toke.dk> (raw)
In-Reply-To: <1571917896021.11761@telenor.com>
<erik.taraldsen@telenor.com> writes:
>> 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.
>
> So in a scenario with a fixed (wall mounted outdoor unit) LTE device
> BQL could work quite well as the radio will not fluctuate too much.
>
> But for a mobil "pocket router" being carried around an AQL approach
> would be needed?
Having setup such an outdoor-mounted unit, I'd say that it's probably a
bit too optimistic to think that it doesn't fluctuate much. Cell
scheduling parameters (including activity from other stations), as well
as weather, can lead to quite significant fluctuations even in a
physically static setup.
So ideally, you'd want to be able to react to changes in either case.
The firmware should certainly have enough information to do that, but if
you can't get that changed, it may be possible to do something BQL-like
(either AQL, or simply a more dynamic variant of BQL) on the host.
-Toke
next prev parent reply other threads:[~2019-10-24 12:14 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
2019-10-24 11:51 ` erik.taraldsen
2019-10-24 12:14 ` Toke Høiland-Jørgensen [this message]
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=87k18ul4ry.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--cc=erik.taraldsen@telenor.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