From: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Fwd: [Ns-developers] BitTorrent for ns-3: Call for Code Review
Date: Wed, 19 Dec 2012 13:25:35 +0100 [thread overview]
Message-ID: <CAGrdgiXutbZSmCLALZ6UyXcMYypcRaqNG5vnvz-hsm6=_EjW_Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7LYFbZYV2wh1NSXQCK0+qe+MJNWh5-xn3ZHGvv-DZ-7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On Wed, Dec 19, 2012 at 1:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I would like very much to be able to analyze stuff like fq_codel under
> bit torrent like loads.
>
I have some knowledge in this area which may help. You should be aware that
BitTorrent may use uTP which is a TCP alternative that tries to eliminate
bufferbloat. The main difference is that uTP targets a "full line" delay
and adjusts its window size based not only on packet loss, but also on
delay. Line delay is then forwarded back over the ACKs. uTP runs inside UDP.
You may want to analyze both things. I have a hunch fq_codel solves most of
the trouble they had because it eliminates the otherwise standing queue. So
be sure to test TCP-only client models as well as the uTP one.
--
J.
[-- Attachment #2: Type: text/html, Size: 1241 bytes --]
prev parent reply other threads:[~2012-12-19 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50D19D6B.3000809@cs.rwth-aachen.de>
2012-12-19 12:09 ` Dave Taht
2012-12-19 12:25 ` Jesper Louis Andersen [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='CAGrdgiXutbZSmCLALZ6UyXcMYypcRaqNG5vnvz-hsm6=_EjW_Q@mail.gmail.com' \
--to=jesper.louis.andersen@gmail.com \
--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