From: Sebastian Moeller <moeller0@gmx.de>
To: bloat@lists.bufferbloat.net,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [Bloat] Really getting 1G out of ISP?
Date: Tue, 22 Jun 2021 08:12:14 +0200 [thread overview]
Message-ID: <38CC4C4D-AE42-4629-8472-16BCC0DEAFEA@gmx.de> (raw)
In-Reply-To: <20210621210048.628befdb@hermes.local>
On 22 June 2021 06:00:48 CEST, Stephen Hemminger <stephen@networkplumber.org> wrote:
>Is there any consumer hardware that can actually keep up and do AQM at
>1Gbit.
Over in the OpenWrt forums the same question pops up routinely once per week. The best answer ATM seems to be a combination of a raspberry pi4B with a decent USB3 gigabit ethernet dongle, a managed switch and any capable (OpenWrt) AP of the user's liking. With 4 arm A72 cores the will traffic shape up to a gigabit as reported by multiple users.
>It seems everyone seems obsessed with gamer Wifi 6. But can only do
>300Mbit single
>stream with any kind of QoS.
IIUC most commercial home routers/APs bet on offload engines to do most of the heavy lifting, but as far as I understand only the NSS cores have a shaper and fq_codel module....
>
>It doesn't help that all the local ISP's claim 10Mbit upload even with
>1G download.
>Is this a head end provisioning problem or related to Docsis 3.0 (or
>later) modems?
For DOCSIS the issue seems to be an unfortunate frequency split between up and downstream and use of lower efficiency coding schemes .
Over here the incumbent cable isp provisions fifty Mbps for upstream and plans to increase that to hundred once the upstream is switched to docsis 3.1.
I believe one issue is that since most of the upstream is required for the reverse ACK traffic for the download and hence it can not be oversubscribed too much.... but I think we have real docsis experts on the list, so I will stop my speculation here...
Regards
Sebastian
>
>_______________________________________________
>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.
next prev parent reply other threads:[~2021-06-22 6:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 4:00 Stephen Hemminger
2021-06-22 6:12 ` Sebastian Moeller [this message]
2021-06-22 7:44 ` Giuseppe De Luca
2021-07-06 22:31 ` Aaron Wood
2021-07-07 2:26 ` Dave Taht
2021-07-07 2:53 ` Aaron Wood
2021-07-08 19:56 ` [Bloat] [Cake] " David P. Reed
2021-06-22 23:04 ` [Bloat] " Livingood, Jason
2021-06-23 15:56 ` Stephen Hemminger
2021-07-06 22:13 ` Aaron Wood
2021-07-06 22:28 ` Wheelock, Ian
2021-07-06 22:40 ` Aaron Wood
2021-07-07 2:10 ` Dave Taht
2021-07-07 9:27 ` Wheelock, Ian
2021-07-07 16:17 ` Jonathan Morton
2021-07-07 16:24 ` Wheelock, Ian
2021-06-22 22:51 ` Livingood, Jason
2021-06-29 19:48 ` Stephen Hemminger
2021-06-29 20:09 ` Sebastian Moeller
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=38CC4C4D-AE42-4629-8472-16BCC0DEAFEA@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=stephen@networkplumber.org \
/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