From: Eric Dumazet <eduma...@google.com> Date: Fri, 10 Jun 2016 16:41:35 -0700
> HTB, CBQ and HFSC pay a very high cost updating the qdisc 'throttled' > status that nothing but CBQ seems to use. > > CBQ usage is flaky anyway, since no qdisc ->enqueue() updates the > 'throttled' qdisc status. > > This looks like some 'optimization' that actually cost more than code > without the optimization, and might cause latency issues with CBQ. > > In my tests, I could achieve a 8 % performance increase in TCP_RR > workload through HTB qdisc, in presence of throttled classes, > and 5 % without throttled classes. Series applied, thanks.
