HN user
the bufferbloat project's end goal is to get to where the default firmware on everything is good out of the box, and that involves trying to fix upstream for the kernel, tools, and distros, so vendors take it and run with it.
I have not had the time to generalize these patches. I do note that alternate ideas for this problem landed in Linux 3.5 which are impossible to backport into Linux 3.3, so I have shelved the idea of working on generalization.
These patches were specific to the ar71xx hardware and unneeded on most other devices.
As for benchmarks, I have not taken the time to publish the results we currently get with fq_codel. However they are better in every respect than our previous attempt with sfqred and comparable to the qfq work we also did. It's not every day you go around seeing orders of magnitude improvements in anything...
http://www.teklibre.com/~d/bloat/pfifo_fast_vs_sfq_qfq_log.p...
(dave taht here)
Given that core components of what we were trying to do (BQL and the codel and fq_codel qdiscs) have only just landed in the mainline linux kernels, doing comprehensive benchmarks would have been misleading.
Secondly - cerowrt's intent is a research project - everything that works we try to get into openwrt - so while the qos implementations differ, both are using fq_codel now.
It's my hope that tomato and gargoyle and dd-wrt - indeed as many router distros - adopt fq_codel or something like it as their underlying qdisc.
http://queue.acm.org/detail.cfm?id=2209336
thirdly - for the kinds of things we are trying to fix (bufferbloat, mesh networks, dns, ipv6) not a lot of good benchmarks exist.