General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "David Täht" <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] a flood of Bufferbloat-related papers
Date: Tue, 11 Oct 2011 12:27:17 +0200	[thread overview]
Message-ID: <4E941A05.2050705@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]

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
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.

I figured I'd just write up a *short* wiki page on the interesting
bufferbloat related papers referenced via google and google scholar.

I was astounded (and delighted) to discover that google scholar had 30+
references, and digging into the later results (google page 2 and
beyond) was fascinating.

http://scholar.google.fr/scholar?start=10&q=bufferbloat&hl=fr&as_sdt=0,5&as_vis=1


I confess that I have not had time to read most of these yet! I've got
"FIFO Service with Differentiated Queueing" loaded on my kindle as I
write, as well as "on the impact of congestion control for concurrent
multipath transfer".

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!

Also a heads-up on work in progress would be helpful, both to avoid
unnecessary duplication of work and to find potential collaborators.

Rather than writing up that list of interesting papers, which google
scholar is doing so well for us already, I'm going to instead start
creating a list of papers and research I'd like to see. I'd appreciate
suggestions...

On my list already would be "an analysis of the effects of broken sack
processing on linux 2.4.24-3.1", of which I *think* I've captured
multiple examples of in the raw traces I've been collecting for
months... (so if anyone is interested in the raw data, I can provide)

I also note that TCP-fit, which was discussed on this mailing list a few
months ago, has a new paper due out this month (if it isn't out already)
in Infocom, Shanghai, October, 2011. I would love to have more
information on this algorithm because I simply cannot believe the
results, as much as I would like to believe them.
http://media.cs.tsinghua.edu.cn/~multimedia/tcp-fit/


-- 
Dave Täht


[-- Attachment #2: dave_taht.vcf --]
[-- Type: text/x-vcard, Size: 204 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


             reply	other threads:[~2011-10-11 10:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 10:27 David Täht [this message]
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

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=4E941A05.2050705@gmail.com \
    --to=dave.taht@gmail.com \
    --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