From: Arie <nospam@ariekanarie.nl>
To: Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Cake] inbound cake or fq_codel shaping fails on cable on netflix reno
Date: Sat, 21 Jul 2018 17:24:51 -0000 [thread overview]
Message-ID: <CAEy8nsT6rBaAodbdmHL=WniBRqAjsdYbVAHt9az9XPs=hxU8qg@mail.gmail.com> (raw)
In-Reply-To: <c9437424d55fdc4a9e7f97e24acfd49f05bd4699.camel@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1176 bytes --]
Two more data points. Shaped my connection to 250Mbit out of the advertised
250Mbit (my usual setting) and shaped to 200Mbit out of the 250Mbit. This
is a pre-linux-net-next cake running on an Edgemax ER4 with
kernel 3.10.107-UBNT.
The regular spikes in ICMP ping is due to the crappy Puma 6 chipset in the
cable modem. UDP is not affected.
On 21 July 2018 at 19:20, Georgios Amanakis <gamanakis@gmail.com> wrote:
> On Sat, 2018-07-21 at 09:09 -0700, Dave Taht wrote:
> >
> > 1) Can someone else on a cablemodem (even without the latest cake,
> > this happens to me on older cake and fq_codel) try this test?
> >
>
> I just tried this on my cable comcast connection. I set ingress to ~80%
> of what fast.com reports when no shaper is in place.
>
> #tc qdisc add dev ens4 root handle 8011 cake bandwidth 16000kbit dual-
> dsthost docsis ingress
> #tc qdisc add dev ens3 root handle 8012 cake bandwidth 2500kbit dual-
> srchost nat docsis ack-filter
>
> I got the same result as you. This is using latest cake.
>
> Georgios
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
>
[-- Attachment #1.2: Type: text/html, Size: 1869 bytes --]
[-- Attachment #2: fast-com-shaped-rate-200-of-250.png --]
[-- Type: image/png, Size: 122500 bytes --]
[-- Attachment #3: fast-com-shaped-rate-250-of-250.png --]
[-- Type: image/png, Size: 128466 bytes --]
next prev parent reply other threads:[~2018-07-21 17:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 16:09 [Cerowrt-devel] " Dave Taht
2018-07-21 17:20 ` [Cerowrt-devel] [Cake] " Georgios Amanakis
2018-07-21 17:23 ` Jonathan Morton
2018-07-21 17:44 ` Georgios Amanakis
2018-07-21 17:47 ` Dave Taht
2018-07-21 18:18 ` Georgios Amanakis
2018-07-21 18:20 ` Dave Taht
2018-07-21 18:23 ` Georgios Amanakis
2018-07-21 20:01 ` Dave Taht
2018-07-21 20:24 ` Jonathan Morton
2018-07-21 20:36 ` Dave Taht
2018-07-21 17:24 ` Arie [this message]
2018-07-21 17:27 ` Dave Taht
2018-07-21 17:28 ` Georgios Amanakis
2018-07-21 17:42 ` Dave Taht
2018-07-21 19:57 ` Toke Høiland-Jørgensen
2018-07-24 2:36 ` Dave Taht
2018-07-24 4:17 ` Georgios Amanakis
2018-07-22 9:57 ` Pete Heist
2018-07-22 10:29 ` 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/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='CAEy8nsT6rBaAodbdmHL=WniBRqAjsdYbVAHt9az9XPs=hxU8qg@mail.gmail.com' \
--to=nospam@ariekanarie.nl \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@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