Jonathan Morton <chromati...@gmail.com> writes: > *That* is why I put in count/2. A multiplicative decrease allows count > to stabilise at some value which adequately controls the queue, rather > than continuously increasing past it. For the typical cake case where > there is one flow per Codel instance and the RTT is of Internet scale, > this should work at least as well as an additive decrease; in > particular, the behaviour is identical where count ended at 2, 3 or 4 > (it can’t end at 1).
Is there any reason why the decrease couldn't be some sort of decay? I.e. a function of how long ago the drop state was exited? -Toke _______________________________________________ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel