Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Kathleen Nichols <nichols@pollere.com>
To: dpreed@reed.com
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] fq_codel is two years old
Date: Thu, 15 May 2014 09:32:57 -0700	[thread overview]
Message-ID: <5374EC39.7040902@pollere.com> (raw)
In-Reply-To: <1400161663.82913275@apps.rackspace.com>


Gosh, that's high praise. And what's really neat is that this was such a
team effort
where we don't even necessarily know each other! What's perhaps bad is that
this was a "volunteer" effort, though that also is a strength. I'm not
sure the
answer is for everyone to work for Google.

On 5/15/14 6:47 AM, dpreed@reed.com wrote:
...
> 
> The solution du jour is to leave bufferbloat in place, while using the
> real fads: prioritization (diffserv once we have the "fast lanes" fully
> legal) and "software defined networking" appliances that use DPI for
> packet routing and traffic management.
>

I think diffserv could be used for good instead of evil.

>  
> 
> Fixing buffer bloat allows the edge- and enterprise- networks to be more
> efficient, whereas not fixing it lets the edge networks move users up to
> more and more expensive "plans" due to frustration and to sell much more
> gear into Enterprises because they are easy marks for complex gadgets.
> 
>  

The above is exactly what Van told me when he was trying to get me to
"paint the fence" of working on aqm again. (That volunteer effort again:
his employer at that time was not paying him to do this sort of thing, so
he had to interest someone to work with him.) I hope you people with big
platforms will continue to try to educate folks.

	Kathie

  reply	other threads:[~2014-05-15 16:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ACF89699-67A0-4853-843F-CAC9BDE97CCB@gmail.com>
2014-05-14 21:01 ` [Cerowrt-devel] " Rich Brown
2014-05-14 22:32   ` [Cerowrt-devel] [Bloat] " Kathleen Nichols
2014-05-15  1:25     ` Dave Taht
2014-05-15 13:47       ` dpreed
2014-05-15 16:32         ` Kathleen Nichols [this message]
2014-05-15 20:32           ` dpreed
2014-05-15 22:53             ` Jonathan Morton
2014-05-16  9:38               ` Michael Welzl
2014-05-16 14:52             ` Valdis.Kletnieks
2014-05-16 16:06               ` Jim Gettys
2014-05-16 20:17                 ` dpreed
2014-05-15 23:46         ` David Lang
2014-05-16  1:01           ` dpreed
2014-05-16  1:13             ` Dave Taht
2014-05-16  1:15             ` David Lang
2014-05-16  3:16               ` David P. Reed
2014-05-16  3:23                 ` David Lang
2014-05-16 12:33                   ` David P. Reed
2014-05-16 14:21                   ` David P. Reed

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=5374EC39.7040902@pollere.com \
    --to=nichols@pollere.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    /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