> On Jan 4, 2019, at 11:34 PM, Toke Høiland-Jørgensen wrote:
>
> Pete Heist writes:
>
> This basically means that we can't use CAKE as a leaf qdisc with GSO
> splitting as it stands currently. I *think* the solution is for CAKE to
> notify its parents; could you try the patch below and see if
Pete Heist writes:
>> On Jan 4, 2019, at 10:34 PM, Toke Høiland-Jørgensen wrote:
>>
>> Pete Heist writes:
>>
>>> Ok, the lockup goes away if you use no-split-gso on the cake qdiscs for the
>>> default traffic (noted below in the drr and hfsc cases with "!!! must use
>>> no-split-gso here
> On Jan 4, 2019, at 11:10 PM, Pete Heist wrote:
>
> Ok, fwiw one doesn’t actually need a one-armed router or VLANs to reproduce
> this. Just do this:
>
> tc qdisc add dev $IFACE root handle 1: hfsc default 1
> tc class add dev $IFACE parent 1: classid 1:1 hfsc ls rate $RATE ul rate $RATE
>
Pete Heist writes:
> Ok, the lockup goes away if you use no-split-gso on the cake qdiscs for the
> default traffic (noted below in the drr and hfsc cases with "!!! must use
> no-split-gso here !!!"). Only I’d like my 600 μs back. :)
>
> This smells of a bug Toke fixed on Sep 12, 2018 in
>
> On Jan 3, 2019, at 2:02 PM, Pete Heist wrote:
>
> I tried iperf3 in UDP mode, but cake is treating these flows aggressively. I
> get the impression that cake penalizes flows heavily that do not respond to
> congestion control signals. If I pit one 8 TCP flows against a single UDP
> flow at
> On Jan 4, 2019, at 3:08 AM, Georgios Amanakis wrote:
>
> On Thu, 2019-01-03 at 23:06 +0100, Pete Heist wrote:
>> Both have cake at 100mbit only on egress, with dual-srchost on client
>> and dual-dsthost on server. With this setup (and probably previous
>> ones, I just didn’t test it this
