From: John Heffner <johnwheffner@gmail.com>
To: Dominik Kaspar <dokaspar.ietf@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Carsten Wolff <carsten@wolffcarsten.de>,
netdev@vger.kernel.org
Subject: Re: Linux TCP's Robustness to Multipath Packet Reordering
Date: Tue, 26 Apr 2011 16:16:15 -0400 [thread overview]
Message-ID: <BANLkTikoQfbSxnJi_OR+N6sa5iVNcTO6Ug@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikjcd6ZAF5wH_8CKA_OCrfprGokmw@mail.gmail.com>
First, TCP is definitely not designed to work under such conditions.
For example, assumptions behind RTO calculation and fast retransmit
heuristics are violated. However, in this particular case my first
guess is that you are being limited by "cwnd moderation," which was
the topic of recent discussion here. Under persistent reordering,
cwnd moderation can inhibit the ability of cwnd to grow.
Thanks,
-John
On Tue, Apr 26, 2011 at 2:00 PM, Dominik Kaspar <dokaspar.ietf@gmail.com> wrote:
> Hi Eric,
>
> Here are the tcpdump files for the first TSO-disabled experiment, in a
> full version and a short version with only the first 10000 packets:
>
> http://home.simula.no/~kaspar/static/mptcp-emu-wlan-hspa-01-tos0-exp1-full.pcap
> http://home.simula.no/~kaspar/static/mptcp-emu-wlan-hspa-01-tos0-exp1-short.pcap
>
> By the way, the packets are sent from the server (x.x.x.189) to the
> client interfaces (x.x.x.74) and (x.x.x.216) with the following
> pattern (which is a non-bursty 128-bit approximation of scheduling
> with a 600:400 ratio over primary path 0 and secondary path 1):
>
> 0010010100101001010010100101001010010100101001010010100101001010
> 0101001010010100101001010010100101001010010100101001010010100101
>
> Greetings,
> Dominik
>
> On Tue, Apr 26, 2011 at 7:10 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> Le mardi 26 avril 2011 à 18:58 +0200, Dominik Kaspar a écrit :
>>> Hi Eric,
>>>
>>> On Mon, Apr 25, 2011 at 5:38 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>>> >
>>> > Since you have at sender a rule to spoof destination address of packets,
>>> > you should make sure you dont send "super packets (up to 64Kbytes)",
>>> > because it would stress the multipath more than you wanted to. This way,
>>> > you send only normal packets (1500 MTU).
>>> >
>>> > ethtool -K eth0 tso off
>>> > ethtool -K eth0 gso off
>>> >
>>> > I am pretty sure it should help your (atypic) workload.
>>>
>>> I made new experiments with the exact same multipath setup as before,
>>> but disabled TSO and GSO on all involved Ethernet interfaces. However,
>>> this did not seem to change much about TCP's behavior when packets are
>>> striped over heterogeneous paths. You can see the results of four
>>> 20-minute experiments on this plot:
>>>
>>> http://home.simula.no/~kaspar/static/mptcp-emu-wlan-hspa-01-tos0.png
>>>
>>> Cheers,
>>> Dominik
>>
>> Hi Dominik
>>
>> Any chance to have a pcap file from sender side, of say first 10.000
>> packets ?
>>
>>
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-04-26 20:16 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 [this message]
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
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=BANLkTikoQfbSxnJi_OR+N6sa5iVNcTO6Ug@mail.gmail.com \
--to=johnwheffner@gmail.com \
--cc=carsten@wolffcarsten.de \
--cc=dokaspar.ietf@gmail.com \
--cc=eric.dumazet@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;
as well as URLs for NNTP newsgroup(s).