[Cake] Correct 'change' behaviour

Kevin Darbyshire-Bryant kevin at darbyshire-bryant.me.uk
Tue Nov 3 08:11:57 EST 2015

On 03/11/15 12:59, Toke Høiland-Jørgensen wrote:
> So we've seen a couple of issues with reconfiguration being weird (i.e.
> retaining previous values). Looking at the code in cake_change() and the
> iproute2 code, this seems to stem from the fact that tc only sets the
> parameters (in the netlink message) that are actually specified on the
> command line, and the kernel only changes the parameters specified in
> the netlink message.
> This leads to the different behaviour: On init, not specifying a
> parameter means "give me a sensible default", whereas on a reconfigure
> it means "don't change this parameter from its current value". This is
> obviously inconsistent. I'd argue that the right thing to do is the
> former in all cases; is there any reason why that would not be the case?
> If not, I'll go fix it :)

Interestingly I think the opposite.  On a change parameters should be
left alone unless they're the thing I'm changing.  It's a 'change' to an
instantiation, *not* an instantiation if you get my drift.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4816 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.bufferbloat.net/pipermail/cake/attachments/20151103/1a408182/attachment-0002.bin>

More information about the Cake mailing list