Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: dickroy@alum.mit.edu
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
	Simon Barber <simon@superduper.net>,
	 starlink@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] [Bloat] Of interest: Comcast AQM Paper
Date: Sat, 7 Aug 2021 13:31:44 -0700	[thread overview]
Message-ID: <CAA93jw4DKnM72CUiL4tnJQyaZUeW_LduJtjkC-Aee--qMZrtoQ@mail.gmail.com> (raw)
In-Reply-To: <649DC4B024D74B8BA6926ABFCD52DC79@SRA6>

On Sun, Aug 1, 2021 at 2:40 PM Dick Roy <dickroy@alum.mit.edu> wrote:
>
> I assume by WiFi what is really meant is devices that have at least one WiFi (layer 1/layer 2) interface. While there are queues in the MAC sublayer, there is really no queue management functionality ... yet ... AFAIK. I know IEEE P802.11bd in conjunction w/ IEEE 1609 is working on implementing a few rudimentary queue mgmt functions.

Thx for the steer to the relevant stds orgs. I dread discovering what
they are up to... However, there is plenty of queue management at the
txop layer.  The structure we put into the linux softmac layer is
described in "ending the anomaly":

The wifi management layer, however, is largely unmanaged, and in some
dense circumstances wifi mgmt frames have been observed to be eating
the most of the airtime available.
>
> That said, seems any AQM in such devices would more than likely be in layer 3 and above.
>
> RR
>
> -----Original Message-----
> From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf Of Livingood, Jason
> Sent: Sunday, August 1, 2021 1:20 PM
> To: Simon Barber
> Cc: starlink@lists.bufferbloat.net; bloat
> Subject: Re: [Starlink] [Bloat] Of interest: Comcast AQM Paper
>
> WiFi is a different challenge as you know. In this case it varies depending on the radio chipset vendor and is on my list of things to work on...
>
> JL
>
> On 7/31/21, 13:50, "Simon Barber" <simon@superduper.net> wrote:
>
>     Awesome to hear that you are turning this on both upstream and downstream. Do you know if the wifi stacks in your home routers also have AQM?
>
>     Simon
>
>
>     > On Jul 30, 2021, at 10:28 PM, Livingood, Jason via Bloat <bloat@lists.bufferbloat.net> wrote:
>     >
>     > FYI that I will be presenting a lightning talk at the IRTF MAPRG meeting today at 17:30 ET (https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/111/materials/agenda-111-maprg__;!!CQl3mcHX2A!XLFMYPw-gnJgHzz_1nF-N7dNeIeT4QD-5wQny8vdAfYE6bzHtVQD3-lqiQI9YwAncrZUew$ ). The talk links to a just-published paper at https://urldefense.com/v3/__https://arxiv.org/abs/2107.13968__;!!CQl3mcHX2A!XLFMYPw-gnJgHzz_1nF-N7dNeIeT4QD-5wQny8vdAfYE6bzHtVQD3-lqiQI9YwCePfNyng$  (click PDF link in upper right of page) that will likely be of interest to these two lists.
>     >
>     > High-level: turning on AQM in the cable modem (upstream queue) took working latency from around 250 ms to between 15-30 ms, which is actually kind of cool. ;-) AQM is turned on in all of our CMTSes (downstream queue) and in DOCSIS 3.1 modems (upstream queue).
>     >
>     > Have a nice weekend,
>     > Jason
>     >
>     > _______________________________________________
>     > Bloat mailing list
>     > Bloat@lists.bufferbloat.net
>     > https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!XLFMYPw-gnJgHzz_1nF-N7dNeIeT4QD-5wQny8vdAfYE6bzHtVQD3-lqiQI9YwCIw2ZGww$
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink



--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw

Dave Täht CEO, TekLibre, LLC

  parent reply	other threads:[~2021-08-07 20:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-01 20:20 Livingood, Jason
2021-08-01 21:39 ` Dick Roy
2021-08-04 11:49   ` Jonathan Morton
2021-08-04 12:46     ` Mikael Abrahamsson
2021-08-04 13:03       ` Sebastian Moeller
2021-08-04 13:06         ` Mikael Abrahamsson
2021-08-04 13:43           ` Sebastian Moeller
2021-08-04 18:28             ` Jonathan Morton
2021-08-04 20:44               ` David Lang
2021-08-04 20:51               ` Sebastian Moeller
2021-08-04 18:31           ` Juliusz Chroboczek
2021-08-04 18:58             ` Jonathan Morton
2021-08-04 20:08               ` Jonathan Bennett
2021-08-04 20:18                 ` Nathan Owens
2021-08-04 20:46                   ` Jonathan Bennett
2021-08-05  0:24                     ` Michael Richardson
2021-08-05 15:11                       ` Frank Carmickle
2021-08-07 23:59                         ` Michael Richardson
2021-08-07 20:31   ` Dave Taht [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-01 20:21 Livingood, Jason
2021-07-30 21:28 [Starlink] " Livingood, Jason
2021-07-31 17:50 ` [Starlink] [Bloat] " Simon Barber
2021-07-31 19:26   ` Aaron Wood
2021-07-31 22:55     ` Neal Cardwell
2021-08-01 13:13       ` Michael Richardson

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/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw4DKnM72CUiL4tnJQyaZUeW_LduJtjkC-Aee--qMZrtoQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=Jason_Livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dickroy@alum.mit.edu \
    --cc=simon@superduper.net \
    --cc=starlink@lists.bufferbloat.net \
    /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