FQ Codel on Wireless-n¶

Cerowrt was originally started to probe the epidemic of bufferbloat-related problems observed with the current wifi deployments.

That proved too hard, and we went and worked first on fixing ethernet. With BQL and fq_codel we think we've made a real dent in that.

Cerowrt is now experimenting with various forms of fq_codel on top of the wireless stack. The problems in wireless-n are so legion that it's difficult to know where to start.

We anticipate that making wireless and wireless-n work well again will be a multi-year project, requiring a half dozen people to do. We have multiple brilliant folk working on the ideas in their spare time.

• Andrew McGregor - The original minstrel author
• Felix Feitkau (current minstrel maintainer, also maintainer of the ath9k driver)
• Dave Täht

and a few others...

We totally lack a

• QA person
• Test Developer

It bugs us that there are million activations of android a month with a wifi stack that can be so dramatically improved by a variety of queue management techniques - and 10s of millions of APs and 100s of millions of deployed wifi devices, all with problems -

most of which that would benefit HUGELY from the work, and yet we can only work on this in our spare time.

So, lacking funding, in the meantime, we hack.

At the moment, felix is enabling new knobs in the ath9k driver, andrew is working on various ns3 simulations, and Dave is experimenting with reducing hw queue lengths and applying fq_codel on top of wifi in cerowrt.

fq_codel at the qdisc layer for wifi is the "wrong thing" as:

1) Wireless-n does packet aggregation to gain bandwidth. FQ on an AP splits up streams into often non-aggregatable chunks.
2) Reducing the hw queue length has a negative effect on throughput over-all in the current driver design

The principal usage of the fq_codel and hw queue changes in cerowrt 3.3.8-10 and later is to observe how well or how badly codel reacts to sudden, rapid bandwidth changes common in wifi. Losing good aggregation in the short term is a good thing as it normalizes some results.

The "right thing", long term, appears to be:

0) tie the codel aqm and minstrel's rate algorithms together better
1) add per station queues to the wifi stack
2) move codel into the mac80211 layer and make it's maxtarget value account for the number of active stations and their aggregate queue lengths
3) fair queue inside each queue
4) come up with additional sane drop strategies within aggregates
5) Address the hidden management frames problem
6) come up with a way to fund and test the work