From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: dickroy@alum.mit.edu, starlink@lists.bufferbloat.net,
Simon Barber <simon@superduper.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Starlink] Of interest: Comcast AQM Paper
Date: Wed, 4 Aug 2021 14:46:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.2108041445470.13354@uplift.swm.pp.se> (raw)
In-Reply-To: <CAJq5cE0vJdVc=q1QjeTsG5ShdL4rpwVhNWZsVyTRPgfXhXH+ug@mail.gmail.com>
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
next prev parent reply other threads:[~2021-08-04 12:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 20:20 [Bloat] " Livingood, Jason
2021-08-01 21:39 ` [Bloat] [Starlink] " Dick Roy
2021-08-04 11:49 ` Jonathan Morton
2021-08-04 12:46 ` Mikael Abrahamsson [this message]
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-07 20:31 ` Dave Taht
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=alpine.DEB.2.20.2108041445470.13354@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--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