Re: [Cake] Correct 'change' behaviour

[Dave Taht <dave.taht@gmail.com>]

in the general case, I recomend looking at the most current fq_codel
code to see how to do it as right as possible. There were several bugs
found and fixed in it as well....
Dave Täht
I just invested five years of my life to making wifi better. And,
now... the FCC wants to make my work, illegal for people to install.
https://www.gofundme.com/savewifi


On Tue, Nov 3, 2015 at 2:07 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Toke Høiland-Jørgensen <toke@toke.dk> writes:
>
>> as best I can follow the logic in that function, it *should* actually
>> get recreated when those flags are set.
>>
>> So why on earth are the values wrong? Memory initialisation problem?
>
> Well, instrumenting cake with some good old-fashioned printk debug
> statements, it appears that a replace when it's already in place does in
> fact only call cake_change, and not cake_destroy followed by cake_init.
>
> Now *why* that is I'm not entirely sure...
>
> -Toke
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake