From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org,
Vasily Isaenko <vasily.isaenko@oracle.com>,
Neal Cardwell <ncardwell@google.com>,
Yuchung Cheng <ycheng@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: resend: tcp: performance issue with fastopen connections (mss > window)
Date: Fri, 13 Jan 2017 20:07:12 +0300 [thread overview]
Message-ID: <22b07900-2151-a31f-34aa-7fb47c958423@oracle.com> (raw)
In-Reply-To: <1484321734.13165.24.camel@edumazet-glaptop3.roam.corp.google.com>
Hi Eric,
On 13.01.2017 18:35, Eric Dumazet wrote:
> On Fri, 2017-01-13 at 18:01 +0300, Alexey Kodanev wrote:
>> Hi,
>>
>> Got the issue when running LTP/netstress test on localhost with mss
>> greater than the send window advertised by client (right after 3WHS).
>> Here is the testscenario that can reproduce this:
> Hi Alexey
>
> So this is a combination of Fastopen + small window + large MSS ?
Yeah, this happens only in the beginning, after first ack from client.
Later window gets
lager than mss and it doesn't happen.
>
> I would rather not force burning tons of coal or other fossil fuel,
> by making each tcp_sendmsg() done by billions of linux devices more
> expensive, only to accommodate for some LTP test doing something not
> sensible ;)
>
> Fact that you removed one condition in the BUG_ON() might hide another
> issue later in the path.
>
> I would suggest to clamp MSS to half the initial window, but I guess
> this is impractical since window in SYN/SYNACK are not scaled.
> 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?
Thanks,
Alexey
next prev parent reply other threads:[~2017-01-13 17:07 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 [this message]
2017-01-13 17:14 ` Eric Dumazet
2017-01-13 17:32 ` Neal Cardwell
2017-01-13 17:41 ` Eric Dumazet
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=22b07900-2151-a31f-34aa-7fb47c958423@oracle.com \
--to=alexey.kodanev@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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