General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: bloat@lists.bufferbloat.net
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [Bloat] Bufferbloat on 4G Connexion
Date: Wed, 23 Oct 2019 07:56:32 -0400	[thread overview]
Message-ID: <0876C235-C6D3-42B0-9D93-114DB75D4204@gmail.com> (raw)
In-Reply-To: <mailman.865.1571824497.1240.bloat@lists.bufferbloat.net>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]


> On Oct 23, 2019, at 5:54 AM,<erik.taraldsen@telenor.com <mailto:erik.taraldsen@telenor.com>> wrote:
> 
> If you could influence the 4G vendors to de-bloat their equipment, would you recommend BQL, L4S or codel/cake?

I've been enjoying this discussion and wonder whether the work going on in the make-wifi-fast (https://lists.bufferbloat.net/pipermail/make-wifi-fast/) is relevant.

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.

Separately, I also wonder whether the Air Time Fairness algorithm might provide a benefit if the cellphone tower station manufacturers chose to get into the game.

Thanks.

Rich

[-- Attachment #2: Type: text/html, Size: 2300 bytes --]

       reply	other threads:[~2019-10-23 11:56 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 [this message]
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
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=0876C235-C6D3-42B0-9D93-114DB75D4204@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --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