From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dominik Kaspar <dokaspar.ietf@gmail.com>
Cc: Carsten Wolff <carsten@wolffcarsten.de>, netdev@vger.kernel.org
Subject: Re: Linux TCP's Robustness to Multipath Packet Reordering
Date: Tue, 26 Apr 2011 23:17:59 +0200 [thread overview]
Message-ID: <1303852679.2699.13.camel@edumazet-laptop> (raw)
In-Reply-To: <1303852092.2699.11.camel@edumazet-laptop>
Le mardi 26 avril 2011 à 23:08 +0200, Eric Dumazet a écrit :
> Le mardi 26 avril 2011 à 23:04 +0200, Dominik Kaspar a écrit :
>
> > In these experiments, a queue size of 1000 packets was specified. I am
> > aware that this is typically referred to as "buffer bloat" and causes
> > the RTT and the cwnd to grow excessively. The smaller I configure the
> > queues, the more time it takes for TCP to "level up" to the aggregate
> > throughput. By keeping the queues so large, I hope to more quickly
> > identify the reason why TCP is actually able to adjust to the immense
> > multipath reordering. What parameters could be highly relevant, other
> > than the queue size?
> >
>
> losses of course ;)
>
> Real internet is full of packet losses, and probability of these losses
> depends on queue sizes (RED like AQM)
>
>
BTW, netem in linux-2.6.39 contains lot of changes in netem module
commit 661b79725fea030803a89a16cda
(netem: revised correlated loss generator)
This is a patch originated with Stefano Salsano and Fabio Ludovici.
It provides several alternative loss models for use with netem.
This patch adds two state machine based loss models.
http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG
next prev parent reply other threads:[~2011-04-26 21:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 10:37 Linux TCP's Robustness to Multipath Packet Reordering Dominik Kaspar
2011-04-25 11:25 ` Eric Dumazet
2011-04-25 14:35 ` Dominik Kaspar
2011-04-25 15:38 ` Eric Dumazet
2011-04-26 16:58 ` Dominik Kaspar
2011-04-26 17:10 ` Eric Dumazet
2011-04-26 18:00 ` Dominik Kaspar
2011-04-26 20:16 ` John Heffner
2011-04-26 21:27 ` Dominik Kaspar
2011-04-27 9:57 ` Carsten Wolff
2011-04-27 16:22 ` Dominik Kaspar
2011-04-27 16:36 ` Alexander Zimmermann
2011-06-21 11:25 ` Ilpo Järvinen
2011-06-21 11:34 ` Carsten Wolff
2011-06-21 11:46 ` Ilpo Järvinen
2011-04-27 16:48 ` Eric Dumazet
2011-04-27 17:39 ` Yuchung Cheng
2011-04-27 17:53 ` Alexander Zimmermann
2011-04-27 19:56 ` Dominik Kaspar
2011-04-27 21:41 ` Yuchung Cheng
2011-04-28 6:11 ` Alexander Zimmermann
2011-06-19 15:22 ` Dominik Kaspar
2011-06-19 15:38 ` Alexander Zimmermann
2011-06-19 16:25 ` Dominik Kaspar
2011-06-20 10:42 ` Ilpo Järvinen
2011-06-20 12:52 ` Dominik Kaspar
2011-06-21 11:35 ` Ilpo Järvinen
2011-04-26 20:43 ` Eric Dumazet
2011-04-26 21:04 ` Dominik Kaspar
2011-04-26 21:08 ` Eric Dumazet
2011-04-26 21:16 ` Dominik Kaspar
2011-04-26 21:17 ` Eric Dumazet [this message]
2011-04-25 12:59 ` Carsten Wolff
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1303852679.2699.13.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=carsten@wolffcarsten.de \
--cc=dokaspar.ietf@gmail.com \
--cc=netdev@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