Dave Taht writes:
> And now I can comment.
>
> I've added this version to a for_upstream branch in the hope that future
> commits can be kept in sync.
>
> Is there anything more that should be added to the commit message?
> Should I be less snarky?
>
>> while presenting an API simple enough that
On 22 November 2017 at 11:25, Dave Taht wrote:
>
> And now I can comment.
>
> I've added this version to a for_upstream branch in the hope that future
> commits can be kept in sync.
>
> Is there anything more that should be added to the commit message?
> Should I be less snarky?
>
> Dave Taht wri
And now I can comment.
I've added this version to a for_upstream branch in the hope that future
commits can be kept in sync.
Is there anything more that should be added to the commit message?
Should I be less snarky?
Dave Taht writes:
> sch_cake is intended to squeeze the most bandwidth and l
sch_cake is intended to squeeze the most bandwidth and lowest 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 an ISP uplink:
tc qdisc add dev eth0 cake bandwidth 20Mbit nat docsis ack-filter
Cake ca
