General list for discussing Bufferbloat
 help / color / mirror / Atom feed
* Re: [Bloat] The challenge
@ 2012-05-10  8:30 Hal Murray
  2012-05-10 13:12 ` Jim Gettys
  0 siblings, 1 reply; 27+ messages in thread
From: Hal Murray @ 2012-05-10  8:30 UTC (permalink / raw)
  To: bloat; +Cc: Hal Murray


> It is counter-intuitive to keep a queue filled with packets that you might
> drop later - as an engineer you tend to think it is more efficient to drop a
> packet *before* it starts to consume space in your precious queue.  This is
> a good deal of what needs to be solved in wireless drivers ...

On the other hand, if your problem is buffer bloat, maybe the queue space 
isn't so precious.

Yes, I too tend to think that way, but maybe it will sink in if I see a few 
reminders.  Thanks.


-- 
These are my opinions.  I hate spam.




^ permalink raw reply	[flat|nested] 27+ messages in thread
* [Bloat] The challenge
@ 2012-05-09  1:04 Dave Taht
  2012-05-09  2:02 ` Kevin Gross
                   ` (2 more replies)
  0 siblings, 3 replies; 27+ messages in thread
From: Dave Taht @ 2012-05-09  1:04 UTC (permalink / raw)
  To: bloat, codel

Both the acm queue article and jim's blog entry this morning were way
above mensa's standards.

Nobody has attempted to explain the elegant simplicity of the
algorithm itself in the inverse sqrt however!  I have a good grip on
it, and am trying, but can barely explain it to myself. Anyone else
care to dig through the codel code and try to put it into english?

Nice bit in ReadWrite News:

http://www.readwriteweb.com/enterprise/2012/05/good-news-for-solving-bufferbloat-codel-provides-no-knobs-solution.php

Bob Cringley lays down the challenge for us here on the bloat list,
and details the opportunity.

http://www.cringely.com/2012/05/beginning-of-the-end-for-bufferbloat/

He closes with:

"My advice to Cisco, Netgear, D-Link and others is that this could be
an important moment in their businesses if they choose to approach it
correctly. It’s a chance to get all of us to buy new routers, perhaps
new everything. Think of the music industry bonanza when we all
shifted our record libraries from vinyl to CDs. It could be the same
for networking equipment. But for that to happen the vendors have to
finally acknowledge bufferbloat and use their marketing dollars to
teach us all why we should upgrade ASAP. Everybody would win.

Take our money, please."

With the cerowrt project, at least, I've hoped to make that shift
possible, and to some extent... happen.

We have *working code*, and *proof of concept*. What's next? Where do
we go from here?

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

^ permalink raw reply	[flat|nested] 27+ messages in thread

end of thread, other threads:[~2012-05-16  6:09 UTC | newest]

Thread overview: 27+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-10  8:30 [Bloat] The challenge Hal Murray
2012-05-10 13:12 ` Jim Gettys
  -- strict thread matches above, loose matches on Subject: below --
2012-05-09  1:04 Dave Taht
2012-05-09  2:02 ` Kevin Gross
2012-05-09  5:16 ` Simon Barber
2012-05-09  5:40   ` Eric Dumazet
2012-05-09  5:41     ` Dave Taht
2012-05-09 13:04   ` Kevin Gross
2012-05-16  5:55     ` Jonathan Morton
2012-05-16  6:09       ` Eric Dumazet
2012-05-16  6:09       ` Dave Taht
2012-05-09 19:10   ` Roger Jørgensen
2012-05-09 19:15     ` Dave Taht
2012-05-09 19:28       ` Dave Taht
2012-05-09 20:02     ` Simon Barber
2012-05-09 20:06   ` Fred Baker
2012-05-09 21:47     ` Jim Gettys
2012-05-10  2:34 ` Jonathan Morton
2012-05-10  2:37   ` Dave Taht
2012-05-10  6:35     ` David Woodhouse
2012-05-10  6:54       ` Jonathan Morton
2012-05-10  7:02         ` David Woodhouse
2012-05-10 14:25           ` Justin McCann
2012-05-10 14:42             ` David Woodhouse
2012-05-10 15:34               ` Neil Davies
2012-05-14  7:27           ` Jonathan Morton
2012-05-14 13:55             ` David Woodhouse

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox