From: Lawrence Stewart <lstewart@room52.net>
To: "David Täht" <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] a flood of Bufferbloat-related papers
Date: Wed, 12 Oct 2011 18:49:53 +1100 [thread overview]
Message-ID: <4E9546A1.8040602@room52.net> (raw)
In-Reply-To: <4E941A05.2050705@gmail.com>
Hi David,
On 10/11/11 21:27, David Täht wrote:
> I sat down on my vacation last week thinking I would write up a review
> of progress since the bufferbloat effort began back in January, 2011. In
I think we should exercise a bit of caution in relation to saying things
like "the bufferbloat effort started in Jan 2011" - the pre-2011
literature alone (although not using the term "bufferbloat"
specifically) extensively covers the issues, symptoms and a myriad of
solutions for the problem.
> particular, I was interested in discovering to what extent we'd made the
> cross-over not just into other OSes besides Linux (e.g - BSD, windows)
> but into academia.
FWIW, I'm a FreeBSD kernel developer and a PhD student working on
transport layer congestion control. I've been involved in doing a lot of
experimental work related to bufferbloat (we refer to it as "collateral
damage" in our papers) using FreeBSD and Linux.
> In the future I would certainly appreciate the authors of bufferbloat
> related/referencing papers to mention them on this mailing list *as*
> they are published!
Here are a few pointers to relevant papers done by people at the
research centre where I'm studying:
"A rough comparison of NewReno, CUBIC, Vegas and ‘CAIA Delay Gradient’
TCP (v0.1)": http://caia.swin.edu.au/reports/110729A/CAIA-TR-110729A.pdf
"Revisiting TCP Congestion Control using Delay Gradients":
http://www.springerlink.com/content/mq50134631115076/
"Multimedia-unfriendly TCP Congestion Control and Home Gateway Queue
Management": http://dx.doi.org/10.1145/1943552.1943558
"Improved coexistence and loss tolerance for delay based TCP congestion
control": http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=5735714&tag=1
"Collateral Damage: The Impact of Optimised TCP Variants on Real-Time
Traffic Latency in Consumer Broadband Environments":
http://dx.doi.org/10.1007/978-3-642-01399-7_31
Off the top of my head, you should also check out the work done by Nick
McKeown's group (although their focus has been on core routers):
http://yuba.stanford.edu/buffersizing/
There's plenty of other relevant work that I can't think of specifically
right now, but it's out there.
Cheers,
Lawrence
next prev parent reply other threads:[~2011-10-12 7:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 10:27 David Täht
2011-10-11 11:58 ` Steinar H. Gunderson
2011-10-11 12:13 ` Eric Dumazet
2011-10-11 12:18 ` Eric Dumazet
2011-10-11 13:09 ` [Bloat] the observed sack oddity David Täht
2011-10-11 13:11 ` David Täht
2011-10-11 13:33 ` Eric Dumazet
2011-10-11 13:51 ` David Täht
2011-10-11 15:25 ` Justin McCann
2011-10-11 15:37 ` Justin McCann
2011-10-13 18:23 ` Jan Ceuleers
2011-10-13 18:27 ` Eric Dumazet
2011-10-11 12:40 ` [Bloat] a flood of Bufferbloat-related papers David Täht
2011-10-11 12:17 ` David Täht
2011-10-12 7:49 ` Lawrence Stewart [this message]
2011-10-12 8:03 ` David Täht
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=4E9546A1.8040602@room52.net \
--to=lstewart@room52.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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