> ... ‘interval' should generally remain at 100ms and that ‘target' should be > computed at around 5-10% of interval, and preferably closer to 5%.
> Is there a justification for setting the interval outside the guidelines > suggested by CoDel’s authors? The interval is reduced on Tin 2 because it is intended for latency-sensitive traffic, which merits a more aggressive AQM response than for best-effort traffic, which tends to be more throughput-sensitive. This has the happy side-effect of giving an additional incentive to not use latency-sensitive DSCPs for bulk traffic. It looks like you still aren’t using the latest version of tc, as that identifies the three tins as “Bulk”, “Best Effort”, and “Voice”, rather than numerically. - Jonathan Morton _______________________________________________ Cake mailing list Cake@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cake
