General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Richard Brown <richard.e.brown@dartware.com>
To: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: [Bloat] Slashdot!
Date: Thu, 29 Mar 2012 01:55:11 +0000	[thread overview]
Message-ID: <96681122-A994-4D0A-9457-3607DA3B025C@intermapper.com> (raw)

It was good to see bufferbloat mentioned on slashdot...

http://linux.slashdot.org/story/12/03/28/1439227/linux-33-making-a-dent-in-bufferbloat

The OP made a fair query: has anyone benchmarked the bql and sfqred that are in the Linux 3.3 kernel?

The responses were the typical spread of Slashdot responses: some funny, some clueless, some hostile, some way OT.

Our own jg gave a nice (and I thought, civil) response to the comment titled, "oversimplified PR noise ignores decade of research" and that started out, 

'The bufferbloat "movement" infuriates me because it's light on science and heavy on publicity. It reminds me of my dad's story about his buddy who tried to make his car go faster by cutting a hole in the firewall underneath the gas petal so he could push it down further.' http://linux.slashdot.org/comments.pl?sid=2752225&cid=39498867

This sounds about right: bufferbloat is well on its way to being treated seriously: first derided, then ignored, then accepted, then discovered...

Best,

Rich

             reply	other threads:[~2012-03-29  1:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  1:55 Richard Brown [this message]
2012-03-29  5:04 ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=96681122-A994-4D0A-9457-3607DA3B025C@intermapper.com \
    --to=richard.e.brown@dartware.com \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox