From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9E6F43B2A4 for ; Tue, 22 Jun 2021 02:12:21 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1624342339; bh=21hMr4y7FjIbnhdEvHHDaCVfWAba42COxtt+/s3Adow=; h=X-UI-Sender-Class:Date:In-Reply-To:References:Subject:To:From; b=UrfbDi5u0wEkGjSapI7cFhmozx64ZHekirPxP/hd0LvewpcaNpsOYfrEM5R9DHn4f gbfCiQW+U2yauKPUAw9lIeAYji8JyFWYy1F6XpYk1kTTp4akayPLQOxdscTrXberJx SZKHKRLnJlYbwwAo87yJ0skWoRAQTCr8iYuWadDs= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [10.51.138.112] ([80.187.113.112]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MMXQF-1lfH0u2LOp-00JcDE; Tue, 22 Jun 2021 08:12:19 +0200 Date: Tue, 22 Jun 2021 08:12:14 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <20210621210048.628befdb@hermes.local> References: <20210621210048.628befdb@hermes.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: bloat@lists.bufferbloat.net, Stephen Hemminger From: Sebastian Moeller Message-ID: <38CC4C4D-AE42-4629-8472-16BCC0DEAFEA@gmx.de> X-Provags-ID: V03:K1:/zm8l9L+0RzPd6kNfMfjZe4JlOYuHvtxUbejd+P6Oj055M2g0Mn Y8d/vgd69Vw8CZ5T8lGiAurvZf0OtYgJEh5/tFCB6sa4/mPx3N7xRC9ZXaO/G+ubAC6oeoq ILLl5ZRP+XiHvTtSlJw2KQJuKrHd+w3t2VLjBJplI7sO1OM1JndT6fzsfpF7mdiqMzE0mh1 jby5zklabVXevY5VWcppg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:GH7wtcNdS9E=:a58vRp7I9X9zmoI1MdxXrG XaqTEuohAHIvk0phI8byGOnnyCnSo1nN9QJvgRi2fsDoj9v+FPcKkULP6BRyiRDWzZDJixx0F RXB11bJ8zoeTGSCEFXa6Kh00VCEnlOnunCcHFIZZseIIBVVsc2go5HYea1dePhCu9la0TGTCD guQkmbtozQsHKPHEAJrDqjfOIRtcQr/vPxUKMYXNrPkAUX3Z+CcxnigItjaOStv9rsbm70s8/ hJG8XwINsBfn6bzoD+usdEaCUEF71mzuwAS9HJUX5acX70fWdvYF0k9b5U+UZEWpNu/Y0KxI/ FHoUlIGKm45FvM4bypgBa4T5w37nFnQs/SIi1iqNtnJAfkPnqm16BCqY0mrlxSz/LX730FT89 S5ePhEH5mbH4c9SlAWoH8JS7Xh5GqSjmcQR3ZqkUuCpMjtOZszOBW1AL2TUepCWR9SzqM2wZX Ia63yea8lkam790AgvozXqHBue/8hEdglePfdhoZHl3ncI8nKJL7yFFUQu10/K0CQAjxzFK2g 0qUd549CVvFuM+MuRapXX8rDCUdKh0/z2zXNjoyEt/LE8r8IBxsjrt7fd5gF1P2RYCbz9R2Pa ICP33cVCdsET8AVY45hx37MK7I8MVcn1g30ZwNgnGtUqUjqgHLf1v0MKDRcusHzKsvGTfPNg1 SC94m71wfY6ncGN7jvcH13Foao4UySuQ9rkyFw3tGv+64gaXA/JpcV6JzN452EcC5ZQ/e+Vir Xu1WgVgtQ9Od8zTbAF6QD9p4OQm0Pq0p6Pbs88JhWnHCIUoV7vUyEG0nzHJzTRvLl65Z1ptFa vbxfMQpTXhYylZeTq1pJBVOtBUtfE70FVSRKRMCR3id2zuo77TiUEP8ZBM1TtYSHaYN9Y4hLx 3/k6T2sYH02hk86gsExGjUQqU6Y81IActg8ckc7bOsw0WPbp4O7Ay+sMXUAYYAJgGi289sn3F GY5UT49+EXpr20z8pRAerg+SncP9+B5/HYm3kiBQHpyfS0gdjl6UC0j9IpWKIcbMRlM9tzRBq C6QsxMHb53kGD9rKim6M3iWp1CCrKF8caP6lpIs8SQ3WRYZqRUm/czosCbq1h7WkaQoOVP1Du hx8Rq0g9n5JBZLZU2/r8VNTUQkIKUTgrHJl Subject: Re: [Bloat] Really getting 1G out of ISP? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2021 06:12:22 -0000 On 22 June 2021 06:00:48 CEST, Stephen Hemminger wrote: >Is there any consumer hardware that can actually keep up and do AQM at >1Gbit=2E Over in the OpenWrt forums the same question pops up routinely onc= e per week=2E 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 c= apable (OpenWrt) AP of the user's liking=2E With 4 arm A72 cores the will t= raffic shape up to a gigabit as reported by multiple users=2E >It seems everyone seems obsessed with gamer Wifi 6=2E But can only do >300Mbit single >stream with any kind of QoS=2E 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 sh= aper and fq_codel module=2E=2E=2E=2E > >It doesn't help that all the local ISP's claim 10Mbit upload even with >1G download=2E >Is this a head end provisioning problem or related to Docsis 3=2E0 (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 =2E 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= =2E1=2E 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 oversubscribe= d too much=2E=2E=2E=2E but I think we have real docsis experts on the list,= so I will stop my speculation here=2E=2E=2E Regards Sebastian > >_______________________________________________ >Bloat mailing list >Bloat@lists=2Ebufferbloat=2Enet >https://lists=2Ebufferbloat=2Enet/listinfo/bloat --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E