significant queues only form where there is a bottleneck, so there
should not be long cascades of codel actually dropping.
Simon
On 05/09/2012 12:10 PM, Roger Jørgensen wrote:
On Wed, May 9, 2012 at 7:16 AM, Simon Barber<[email protected]> wrote:
One question now remains - will codel AQM be sufficient on it's own in
getting delays down to levels that users are happy with for the common
latency sensitive interactive traffic - VoIP, gaming and Skype for example -
or are the further reductions that can be had with traffic classification
and smart queuing algorithms necessary? The nicest part about codel on it's
own is that it works on opaque packets - it will handle VPNs and traffic
within them nicely. It gets away from all the complexity required to
classify traffic in a world where traffic is often trying to hide.
I'm more worried about how long cascades of codel code in equipment
will work together, add lots of traffic to the mix, just how will it
behave then?
_______________________________________________
Bloat mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/bloat
