From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
Mikael Abrahamsson via Bloat <bloat@lists.bufferbloat.net>,
Jonathan Morton <chromatix99@gmail.com>
Cc: starlink@lists.bufferbloat.net, dickroy@alum.mit.edu,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] [Bloat] Of interest: Comcast AQM Paper
Date: Wed, 04 Aug 2021 15:03:08 +0200 [thread overview]
Message-ID: <5C65BC6E-1ABD-4432-B2CE-AC8BACDA363D@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.20.2108041445470.13354@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
I guess the point is AQM is not really that expensive, even FQ AQM, traffic shaping however is expensive. But for wifi shaping is not required so AQM became feasible.
Regards
Sebastian
On 4 August 2021 14:46:30 CEST, Mikael Abrahamsson via Bloat <bloat@lists.bufferbloat.net> wrote:
>On Wed, 4 Aug 2021, Jonathan Morton wrote:
>
>> 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.
>
>Does this work also with flowoffload enabled, or is that not accelerated
>on for instance MT76? I'm surprised since MT76 can barely do 100 meg/s of
>large packets using only CPU?
>
>--
>Mikael Abrahamsson email: swmike@swm.pp.se
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1889 bytes --]
next prev parent reply other threads:[~2021-08-04 13:03 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 [this message]
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=5C65BC6E-1ABD-4432-B2CE-AC8BACDA363D@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dickroy@alum.mit.edu \
--cc=starlink@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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