From: "David Täht" <dave.taht@gmail.com>
To: Lawrence Stewart <lstewart@room52.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] a flood of Bufferbloat-related papers
Date: Wed, 12 Oct 2011 10:03:48 +0200 [thread overview]
Message-ID: <4E9549E4.3040202@gmail.com> (raw)
In-Reply-To: <4E9546A1.8040602@room52.net>
[-- Attachment #1: Type: text/plain, Size: 3169 bytes --]
On 10/12/2011 09:49 AM, Lawrence Stewart wrote:
> 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.
>
You are correct, I should have said 'bufferbloat.net effort', which got
off the ground in late january, 2011.
We had started on a collection of older papers on the wiki, starting
with rfc970 and working forward. Filling in the blanks between that (and
yes, we can go back further) and the present day is going to take some work!
>> 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.
>
More keywords to google for...
>> 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
>
>
I was aware of 2 of these, but not the others. I would very much like to
read the last in particular, but it doesn't appear to be publicly
available from a quick google.
(And thx for putting the refs into the wiki format!)
> 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/
>
I've read much of their work, and much of it does apply, but home
routers are different in significant ways that I hope to be talking
about at lincs in paris, oct 19...
> There's plenty of other relevant work that I can't think of
> specifically right now, but it's out there.
>
Thanks for the pointers... (all, keep 'em coming)
> Cheers,
> Lawrence
--
Dave Täht
[-- Attachment #2: dave_taht.vcf --]
[-- Type: text/x-vcard, Size: 214 bytes --]
begin:vcard
fn;quoted-printable:Dave T=C3=A4ht
n;quoted-printable:T=C3=A4ht;Dave
email;internet:dave.taht@gmail.com
tel;home:1-239-829-5608
tel;cell:0638645374
x-mozilla-html:FALSE
version:2.1
end:vcard
prev parent reply other threads:[~2011-10-12 8:03 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
2011-10-12 8:03 ` David Täht [this message]
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=4E9549E4.3040202@gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=lstewart@room52.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