From: Jim Gettys <jg@freedesktop.org>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Pointers to useful work on buffer sizing.
Date: Mon, 21 Mar 2011 14:27:24 +0100 [thread overview]
Message-ID: <4D87523C.8090004@freedesktop.org> (raw)
Marina Thottan has been very kind to send me pointers to recent work on router buffer sizing. As you will see, there are good reasons to believe much conventional wisdom is far from the mark.
She is co-author of a survey paper that covers work done by different groups on router buffer sizing. Here is a link to it:
http://portal.acm.org/citation.cfm?id=1517487&CFID=13973251&CFTOKEN=48745519&qualifier=LU1007961
Nick Mckeown @ Stanford has several talks on buffers for routers.
Here is the link to his web page:
http://tiny-tera.stanford.edu/~nickm/talks/index.html
The specific talks are on this page:
"Internet Routers: Past Present and Future."
"Buffers: How we fell in love with them, and why we need a divorce."
"Sizing Router Buffers"
"Network Processors and their memory"
"Designing Packet Buffers for Internet Routers"
"Memories for Internet Routers"
reply other threads:[~2011-03-21 13:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D87523C.8090004@freedesktop.org \
--to=jg@freedesktop.org \
--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