OP was me, actually. *My* benchmarks are showing good results, but they are more limited than I wanted them to be at this point. Also... well I'll get to that in a second.
I had a subtle purpose in pursuing a little pr at this time, as what I thought would happen was that the "Linux-3.3, now with BQL" 'story' would get boiled down to 2-3 issues that weren't necessarily correct or primary.
It is normal in dealing with the press that a story needs to have a hook, conflict and resolution, and only one or two new ideas that need to be bridged to the unknowing reader. Dumping too much new stuff on a generic reporter usually leads to bad results. Thankfully cringley genuinely 'gets it', and can create a hook around anything. He tells a good story.
Within those constraints however is that pesky 'simplify the issue" problem needed to get the core idea across to new audiences.
In observing the responses to cringley's and slashdot's article, exactly what I feared has happened in several respects, and hasn't happened in another.
They are:
0) "Linux-3.3, now with BQL! will solve all your networking problems, curl your hair, and fix your sex life".
:whew: headed that one off at the pass. A 'dent in the bloat'. That works for me.
1) But spurring people into action to do what's doable, seems to be a problem.
This does reinforce our overall deployment desire is that AQMs need to be 'on by default' as well as 'do no harm'.
And I do need to get back to my own efforts to find useful operating ranges for what we got that can be on by default as well as 'do no harm'.
2) "Bufferbloat is a router problem only". We're failing here. Bloat is a potential problem everywhere on the path. In my own environments these days most of it is actually on my laptop, having fixed it on the routers I'm fiddling with.
3) "Bufferbloat is only a linux problem." This is kind of a natural association for a busy reader to make, and thus far we've avoided that particular distillation of the meme. (the spin that I like is that "linux is in the forefront of the battle against bufferbloat")
However it does point out the reverse problem, in that we do want people on other operating systems and vendors to step up, and responses outside the linux and ietf and academic community have been tepid. I would like very much for there to be a good contact within all the big oses and vendors, large and small, known to be paying attention to our efforts, with products in the pipeline, all with fixes...
4) "Getting the story right in the first place". Still a fail. I have alerts for new articles on bloat (several other people must have, too) and nearly every one gets some core detail wrong. Sometimes I worry that the meme will be subverted... take the recent cisco 'win the war against buffering' campaign.
http://blogs.cisco.com/consumer/win-the-war-on-buffering/sigh.
I made a comment. It's still awaiting moderation.
http://huchra.bufferbloat.net/~d/ciscosnark/ciscobloat2.png
I am just going to have to throw one of these routers into the testbed next week and see what happens.
I find gandhi comforting as well. Although I would substitute 'deployed' for discovered, and gandhi was a far, far, far more patient person than I am.
However in the past we've had several people also respond with hostility to the PR effort we've given this issue. While our conversion rate among those we've engaged with patience and data hovers at nearly 100%, and I hope that that poster jg responded to does recheck his facts, I wish there was a way to have a simple message that more immediately engaged people, particularly those outside the computer science field.
People like: governments, managers, VCs and wall street. It really bothers me that the economist hasn't run a story, although bloat did make a nyt blog recently.
What I enjoy tremendously about modern media is that the web commentary can provide additional insight, and analogies, that help map a new idea into the contexts more minds operate in.
This analogy was hysterical:
https://plus.google.com/u/0/107942175615993706558/posts/YGEFa2iKTfwAlso good was:
"one of the only analogs [to how tcp operates] I can think of might be the Blackbird stealth
plane. Leaks like a sieve on the ground, spitting fuel all over the
place, because at altitude the seals expand so much that they'd pop if
it hadn't been designed to leak on the ground. Using gigantic packet
buffers would be like "fixing" a Blackbird so that it didn't leak on the
runway." - via slashdot