From: Jim Gettys <jg@freedesktop.org>
To: bloat@lists.bufferbloat.net, linux-wireless@vger.kernel.org
Subject: [Bloat] Fwd: dynamic wi-fi buffer sizing paper
Date: Mon, 14 Feb 2011 07:07:19 -0500 [thread overview]
Message-ID: <4D591AF7.8030301@freedesktop.org> (raw)
Van Jacobson pointed out the following paper and implementation about
802.11 buffer sizing.
See:
http://www.hamilton.ie/tianji_li/
http://www.hamilton.ie/tianji_li/buffersizing.pdf
If I can ever get a final version of "RED in a different light" out of
Van I'll forward a pointer to the list...
- Jim
-------- Original Message --------
Subject: dynamic wi-fi buffer sizing paper
Date: Thu, 6 Jan 2011 10:50:12 PST
From: Van Jacobson <van@parc.com>
To: Jim Gettys <jg@freedesktop.org>
Jim,
Here's the Doug Leith paper I mentioned. As I said on the phone I
think there's an easier, more robust way to accomplish the same
thing but they have running code and I don't. You can get their
mad-wifi implementation at
http://www.hamilton.ie/tianji_li/buffersizing.html
- van
reply other threads:[~2011-02-14 12:07 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=4D591AF7.8030301@freedesktop.org \
--to=jg@freedesktop.org \
--cc=bloat@lists.bufferbloat.net \
--cc=linux-wireless@vger.kernel.org \
/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