From: Jonathan Morton <chromatix99@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: Wed, 4 Aug 2021 14:49:52 +0300 [thread overview]
Message-ID: <CAJq5cE0vJdVc=q1QjeTsG5ShdL4rpwVhNWZsVyTRPgfXhXH+ug@mail.gmail.com> (raw)
In-Reply-To: <649DC4B024D74B8BA6926ABFCD52DC79@SRA6>
> 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.
>
> That said, seems any AQM in such devices would more than likely be in layer 3 and above.
Linux-based CPE devices have AQM functionality integrated into the
Wifi stack. The AQM itself operates at layer 3, but the Linux Wifi
stack implementation uses information from layers 2 and 4 to improve
scheduling decisions, eg. airtime-fairness and flow-isolation (FQ).
This works best on soft-MAC Wifi hardware, such as ath9k/10k and MT76,
where this information is most readily available to software. In
principle it could also be implemented in the MAC, but I don't know of
any vendor that's done that yet.
- Jonathan Morton
next prev parent reply other threads:[~2021-08-04 11:50 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 [this message]
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
-- 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='CAJq5cE0vJdVc=q1QjeTsG5ShdL4rpwVhNWZsVyTRPgfXhXH+ug@mail.gmail.com' \
--to=chromatix99@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