Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Cisco article about Bufferbloat
Date: Wed, 7 May 2014 09:20:51 -0400	[thread overview]
Message-ID: <C35689EB-E4E9-4ECB-AD2A-11399D06AD82@gmail.com> (raw)

Cisco posted a note re: Bufferbloat and their PIE algorithm the other day. 

I added a comment that gives a little more background about the history of the problem, and acknowledges the work from the Bufferbloat project team, kernel developers, and other industry players to produce a good result.

Read both at: http://newsroom.cisco.com/feature-content?type=webcontent&articleId=1414442

Rich

             reply	other threads:[~2014-05-07 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 13:20 Rich Brown [this message]
2014-05-08 10:17 ` [Cerowrt-devel] [Bloat] " Jesper Dangaard Brouer
2014-05-08 12:50   ` Rich Brown

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=C35689EB-E4E9-4ECB-AD2A-11399D06AD82@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@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