From: Eric Dumazet <eric.dumazet@gmail.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: Eric Dumazet <edumazet@google.com>,
Alexey Kodanev <alexey.kodanev@oracle.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Vasily Isaenko <vasily.isaenko@oracle.com>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: resend: tcp: performance issue with fastopen connections (mss > window)
Date: Fri, 13 Jan 2017 09:41:27 -0800 [thread overview]
Message-ID: <1484329287.13165.40.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <CADVnQykVj0CdHVYkfuogy6nOxfL+ODXue-3siKh_oACCBjVrtg@mail.gmail.com>
On Fri, 2017-01-13 at 12:32 -0500, Neal Cardwell wrote:
> On Fri, Jan 13, 2017 at 12:14 PM, Eric Dumazet <edumazet@google.com> wrote:
> >
> > On Fri, Jan 13, 2017 at 9:07 AM, Alexey Kodanev
> > <alexey.kodanev@oracle.com> wrote:
> > > Hi Eric,
> > > On 13.01.2017 18:35, Eric Dumazet wrote:
> >
> > >> Care to send a packetdrill test so that we have a clear picture of what
> > >> is going on ?
> > >
> > > Is it capable of making two connections in the single test, one after
> > > another?
> >
> > Absolutely.
> >
> > Neal, Yuchung would you be kind enough to send a Fastopen tpacketdrill
> > template showing a typical fastopen test
> > running on an upstream kernel ?
> >
> > Thanks !
>
> Sure, here is an example packetdrill script, IIRC written by Yuchung,
> which demonstrates TCP fast open and consecutive active connections:
>
> `sysctl -q net.ipv4.tcp_timestamps=0`
>
> // Cache warmup: send a Fast Open cookie request
> 0.000 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
> +0 fcntl(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0
> +0 sendto(3, ..., 0, MSG_FASTOPEN, ..., ...) = -1 EINPROGRESS
> (Operation is now in progress)
> +0 > S 0:0(0) <mss 1460,nop,nop,sackOK,nop,wscale 8,FO,nop,nop>
> +.010 < S. 123:123(0) ack 1 win 5840 <mss
> 1040,nop,nop,sackOK,nop,wscale 6,FO abcd1234,nop,nop>
> +0 > . 1:1(0) ack 1
> +0 close(3) = 0
> +0 > F. 1:1(0) ack 1
> +.010 < F. 1:1(0) ack 2 win 92
> +0 > . 2:2(0) ack 2
>
> //
> // TEST1: Servers sends SYN-ACK with data and another two data packets
> //
> +0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 4
> +0 fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
> +0 sendto(4, ..., 1000, MSG_FASTOPEN, ..., ...) = 1000
> +0 > S 0:1000(1000) <mss 1460,nop,nop,sackOK,nop,wscale 8,FO
> abcd1234,nop,nop>
> +.010 < S. 1000000:1001400(1400) ack 1001 win 5840 <mss
> 1040,nop,nop,sackOK,nop,wscale 6>
> +0 < . 1401:2801(1400) ack 1001 win 257
> +0 < P. 2801:3001(200) ack 1001 win 257
>
> neal
Thanks Neal
Also worth adding that packetdrill has the following option to tune the
MTU on the tun device :
--mtu=xxxxx
next prev parent reply other threads:[~2017-01-13 17:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 15:01 resend: tcp: performance issue with fastopen connections (mss > window) Alexey Kodanev
2017-01-13 15:35 ` Eric Dumazet
2017-01-13 17:07 ` Alexey Kodanev
2017-01-13 17:14 ` Eric Dumazet
2017-01-13 17:32 ` Neal Cardwell
2017-01-13 17:41 ` Eric Dumazet [this message]
2017-01-18 17:32 ` Alexey Kodanev
2017-01-18 17:35 ` Eric Dumazet
2017-01-18 18:13 ` Yuchung Cheng
2017-01-18 18:16 ` Eric Dumazet
2017-01-18 18:27 ` Yuchung Cheng
2017-01-18 18:42 ` Neal Cardwell
2017-01-18 18:33 ` Neal Cardwell
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=1484329287.13165.40.camel@edumazet-glaptop3.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=alexey.kodanev@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=vasily.isaenko@oracle.com \
--cc=ycheng@google.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