From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Mikael Abrahamsson via Bloat <bloat@lists.bufferbloat.net>,
Jonathan Morton <chromatix99@gmail.com>,
starlink@lists.bufferbloat.net, dickroy@alum.mit.edu
Subject: Re: [Bloat] [Starlink] Of interest: Comcast AQM Paper
Date: Wed, 4 Aug 2021 15:43:04 +0200 [thread overview]
Message-ID: <8393833B-BE11-4B97-92CC-95C2B48305B9@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.20.2108041504480.13354@uplift.swm.pp.se>
Hi Mikael,
> On Aug 4, 2021, at 15:06, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Wed, 4 Aug 2021, Sebastian Moeller wrote:
>
>> 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.
>
> My point is that CPU based forwarding has very bad performance on some platforms, regardless if you're doing shaping, AQM or none of them (FIFO).
>
> If it's not hw accelerated, it sucks.
>
> When I did tests on MT7621 it did ~100 meg/s without flow-offload, and full gig with it.
Reminds me of the joke of the gent sitting in a pub boasting the size of his property being so immense it takes a full week to ride around the perimeter...
To which another guest responds wryly, he used to have a horse that slow in the past as well....
Point being a number of commercially sold CPE are not fit for the job of doing anything at Gbps link rates... sure accelerators can be nice, but they all come at the expense of reduced generality... Give that a raspberry Pi 4B has no trouble doing traffic shaping a 1Gbps (plus firewalling, NAT, PPPoE, ... and all of this in "software" with full generality) there is little excuse of still selling deploying CPE that were a decent fit for DSL link rates... But I live in a rich country where ISP take 2-5 EUR rent per month for CPE, so money is not a reasonable excuse for an ISP over here to cut corners....
Regards
Sebastian
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2021-08-04 13:43 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
2021-08-04 13:03 ` Sebastian Moeller
2021-08-04 13:06 ` Mikael Abrahamsson
2021-08-04 13:43 ` Sebastian Moeller [this message]
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=8393833B-BE11-4B97-92CC-95C2B48305B9@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