doesn't have a drop down option for "docsis" or
"cable" at the linklayer for cake. (I guess I'd use "cable" rather than docsis)
aside from that cake is working great. Peaks out at 100mbit on the archer-c7-v2
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
This is consistent with the other multi-word parameters. Also change the
JSON output to be consistent with way it is formatted for the other
options.
Signed-off-by: Toke Høiland-Jørgensen
---
man/man8/tc-cake.8 | 4 ++--
tc/q_cake.c| 8
2 files changed, 6 insertions(+), 6
David Ahern writes:
> On 7/19/18 7:56 AM, Toke Høiland-Jørgensen wrote:
>> sch_cake is intended to squeeze the most bandwidth and latency out of even
>> the slowest ISP links and routers, while presenting an API simple enough
>> that even an ISP can configure it.
>>
>> Example of use on a cable
On 7/19/18 7:56 AM, Toke Høiland-Jørgensen wrote:
> sch_cake is intended to squeeze the most bandwidth and latency out of even
> the slowest ISP links and routers, while presenting an API simple enough
> that even an ISP can configure it.
>
> Example of use on a cable ISP uplink:
>
> tc qdisc
Kevin Darbyshire-Bryant writes:
> Hiya Chaps,
>
> Bet that subject woke you up!
>
> This is one for the back burner but I’d like to do it at some point,
> mainly ‘cos my name is in the maintainer field :-)
>
> Ideally I’d like to introduce cake as a kernel patch backport to
> openwrt instead of
> On 19 Jul, 2018, at 6:53 pm, Kevin Darbyshire-Bryant
> wrote:
>
> …the conditional conntrack has me beaten.
Given the focus of OpenWRT, it might be sane to just unconditionally depend on
conntrack in the backported version.
- Jonathan Morton
sch_cake is intended to squeeze the most bandwidth and latency out of even
the slowest ISP links and routers, while presenting an API simple enough
that even an ISP can configure it.
Example of use on a cable ISP uplink:
tc qdisc add dev eth0 cake bandwidth 20Mbit nat docsis ack-filter
To shape
Hiya Chaps,
Bet that subject woke you up!
This is one for the back burner but I’d like to do it at some point, mainly
‘cos my name is in the maintainer field :-)
Ideally I’d like to introduce cake as a kernel patch backport to openwrt
instead of as an additional module. I’ve started out but
On 7/19/18 9:20 AM, Toke Høiland-Jørgensen wrote:
> David Ahern writes:
>
>> On 7/19/18 4:53 AM, Toke Høiland-Jørgensen wrote:
>>> A few comments below; will fix the rest.
>>>
> + print_uint(PRINT_JSON, "bandwidth", NULL, bandwidth);
> +
David Ahern writes:
> On 7/19/18 4:53 AM, Toke Høiland-Jørgensen wrote:
>> A few comments below; will fix the rest.
>>
+ print_uint(PRINT_JSON, "bandwidth", NULL, bandwidth);
+ print_string(PRINT_FP, NULL, "bandwidth %s ",
sprint_rate(bandwidth,
On 7/19/18 4:53 AM, Toke Høiland-Jørgensen wrote:
> A few comments below; will fix the rest.
>
>>> + print_uint(PRINT_JSON, "bandwidth", NULL, bandwidth);
>>> + print_string(PRINT_FP, NULL, "bandwidth %s ",
>>> sprint_rate(bandwidth, b1));
>>> + }
sch_cake is intended to squeeze the most bandwidth and latency out of even
the slowest ISP links and routers, while presenting an API simple enough
that even an ISP can configure it.
Example of use on a cable ISP uplink:
tc qdisc add dev eth0 cake bandwidth 20Mbit nat docsis ack-filter
To shape
It looks like backporting this to openwrt would be a pita, but a
potential 10% improvement to inbound shaping is not to be sneezed at
(and I imagine it could be better than that for non-intel
cache-crippled routers)
-- Forwarded message -
From: Paolo Abeni
Date: Thu, Jul 19, 2018
A few comments below; will fix the rest.
>> +print_uint(PRINT_JSON, "bandwidth", NULL, bandwidth);
>> +print_string(PRINT_FP, NULL, "bandwidth %s ",
>> sprint_rate(bandwidth, b1));
>> +} else
>> +print_string(PRINT_ANY,
14 matches
Mail list logo
