Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Wheelock, Ian" <ian.wheelock@commscope.com>
To: Sebastian Moeller <moeller0@gmx.de>,
	Kenneth Porter <shiva@sewingwitch.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] tp-link request for SQM
Date: Fri, 3 Dec 2021 12:12:59 +0000	[thread overview]
Message-ID: <371F0599-5E79-4D9A-9156-C254B29DDCDF@commscope.com> (raw)
In-Reply-To: <C3EBDFE9-4EB9-4F2A-8EDB-A4ED1BB46B5D@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 4787 bytes --]

Hi
280Mbps service with Comcast is likely the 300/10 package offering… In that case the US is limited to 10Mbps

I understand there might be some issue if 280Mbps was being processed – but in the US direction, we are not talking >>100Mbps – its about 10Mbps US, I would have thought running cake on 10Mbps US cake would not have triggered a 50% loss in performance even on this platform. Now if cake is applied to both inbound and outbound traffic then having to deal with ~280Mbps might be tough. In the case of DOCSIS AQM, PIE runs in the GW only on outbound traffic.



From: Bloat <bloat-bounces@lists.bufferbloat.net> on behalf of Sebastian Moeller <moeller0@gmx.de>
Date: Friday 3 December 2021 at 10:40
To: Kenneth Porter <shiva@sewingwitch.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tp-link request for SQM

> On Dec 3, 2021, at 11:10, Kenneth Porter wrote: > > --On Thursday, December 02, 2021 10:48 AM -0800 Dave Taht wrote: > >> tp-link, is, so far as I know,
External (moeller0@gmx.de<mailto:moeller0@gmx.de>)
  Report This Email<https://protection.inkyphishfence.com/report?id=Y29tbXNjb3BlL2lhbi53aGVlbG9ja0Bjb21tc2NvcGUuY29tLzg5ODdjNTNmZWEyNTcwMzY0NzhkMzQxNjY1YmE3YjRmLzE2Mzg1MjgwNDkuODQ=#key=a3e94f965af0f0f0acc4bf74d04b930a>  FAQ<https://www.inky.com/banner-faq/>  Protection by INKY<https://www.inky.com>






> On Dec 3, 2021, at 11:10, Kenneth Porter <shiva@sewingwitch.com> wrote:

>

> --On Thursday, December 02, 2021 10:48 AM -0800 Dave Taht <dave.taht@gmail.com> wrote:

>

>> tp-link, is, so far as I know, the last major home router vendor NOT

>> shipping a SQM system. Perhaps this could be modded up with someones

>> with accounts?

>>

>> https://secure-web.cisco.com/11xOUC1zY509JqNeDmjflwH4rSaowAKbPpsMSSKsLaElYT5bKwUqpCvIP8pSIJN0xDSludBbilZxiCWeGyX9QBVXQIYGg4aeJlOIvbdBnAe-AGULG-eanWnKwFWAYCjRhnT-GbDz2UCRsr4YTmHkHQVjfSafvUq4KtMTkOBAhmvbMckt7aS8HDyLXxNQDxuTyJebXHYNYvNKVXNoeU562qbXBhB-ud2slR8bxmp5SrW2zaA0BTM-dK0S4ryLxffAxnZ4JjFcLRpX1I4xL1vIy1r3HCDpAwFidpPnHP-jznaHho4VzKVmEn5T4fAgYwSA-_7WEx2qqWgizSp8HE-kOmQ/https%3A%2F%2Fcommunity.tp-link.com%2Fus%2Fhome%2Fforum%2Ftopic%2F511156

>

> I just signed up an account and will add my vote.

>

> I just bought an Archer 20 to replace my old 2016 Zyxel running OpenWrt. I'd found it by looking at various reviews of "best OpenWrt router for 2021". I just updated my Zyxel firmware from v18 to v20 firmware. I get about 280 Mbps from Xfinity. I turned on cake and it dropped by 50%! So I think the old router's CPU isn't up to it. I'll be swapping in the TP-Link soon so I can turn on cake without the big performance hit.



        Getting low latency traffic shaping to work in a robust and reliable way above say ~100Mbps is still a challenge even for relatively recent router SoCs. Modern multicore SoCs upped the ante in the things-to-look-out for area by adding CPU power-saving (especially frequency scaling) and load distribution over CPUs to the mix... Now even something like a raspberry pi 4B with an additional well-selected USB3 gigabit ethernet dongle (costing less than 100 EUR all in all) will allow cake up to 1/1 Gbps but still requires careful configuration to do so. No idea whether an archer 20 will do (not even sure what model that is, here in Germany I see either an C20 or an AX20 but no plain unadorned 20). If you should try OpenWrt on that thing, the OpenWrt forum is a good place to ask for configuration advice for specific models (will obviously not help if you stick to the manufacturer's firmware).



Regards

        Sebastian







>

>

> _______________________________________________

> Bloat mailing list

> Bloat@lists.bufferbloat.net

> https://secure-web.cisco.com/1Z2y8NhzIa813o53EO2ZaEd_c84yx8078Yt5QdXENdHS1zmXuEmxrBiiVcTtdPd4aSueQwqb1LNjPUC-JPnSHnunQLYhMUg22HKM9c9d41a17ITcIQIU9SxTj9fXsDo6olgiCfxxZgURhHnL8RQdjc486i3YRR9svzSz_KqH8OqaQhVOQhIREqb0yVIX8pWWTdwbNIA5EXM7uey0j1C8KlC12QVTerBPM9DQTHbebjUnM0iShNbvfDEl4lZFVkCtwIDrSdcbbb0r5c-sfl-dDCDlAwQuB9wgWpJO8j41FeDE1ckiZJtbNpKTZo1MJuEEFpP2DYfe-iskti5Znw5LRtA/https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat



_______________________________________________

Bloat mailing list

Bloat@lists.bufferbloat.net

https://secure-web.cisco.com/1Z2y8NhzIa813o53EO2ZaEd_c84yx8078Yt5QdXENdHS1zmXuEmxrBiiVcTtdPd4aSueQwqb1LNjPUC-JPnSHnunQLYhMUg22HKM9c9d41a17ITcIQIU9SxTj9fXsDo6olgiCfxxZgURhHnL8RQdjc486i3YRR9svzSz_KqH8OqaQhVOQhIREqb0yVIX8pWWTdwbNIA5EXM7uey0j1C8KlC12QVTerBPM9DQTHbebjUnM0iShNbvfDEl4lZFVkCtwIDrSdcbbb0r5c-sfl-dDCDlAwQuB9wgWpJO8j41FeDE1ckiZJtbNpKTZo1MJuEEFpP2DYfe-iskti5Znw5LRtA/https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat

[-- Attachment #2: Type: text/html, Size: 9811 bytes --]

  reply	other threads:[~2021-12-03 12:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 18:48 [Cerowrt-devel] " Dave Taht
2021-12-03 10:10 ` [Cerowrt-devel] [Bloat] " Kenneth Porter
2021-12-03 10:40   ` Sebastian Moeller
2021-12-03 12:12     ` Wheelock, Ian [this message]
2021-12-03 12:43       ` Kenneth Porter
     [not found]       ` <A5CB878868B38B2F0660B051@192.168.1.16>
2021-12-03 14:23         ` Dave Taht
2021-12-03 12:38     ` Kenneth Porter
2021-12-03 11:59 ` Luca Muscariello
2021-12-03 14:18   ` [Cerowrt-devel] " Dave Taht
2021-12-03 14:35     ` Sebastian Moeller
2021-12-03 14:58       ` Luca Muscariello
2021-12-09 16:09         ` Sebastian Moeller
2021-12-09 17:38           ` Luca Muscariello
2021-12-09 18:23             ` Sebastian Moeller
2021-12-09 18:54               ` Luca Muscariello

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=371F0599-5E79-4D9A-9156-C254B29DDCDF@commscope.com \
    --to=ian.wheelock@commscope.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=shiva@sewingwitch.com \
    /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