From: Eric Dumazet <eric.dumazet@gmail.com>
To: sj38.park@gmail.com, edumazet@google.com
Cc: davem@davemloft.net, aams@amazon.com, ncardwell@google.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, shuah@kernel.org,
ycheng@google.com, David.Laight@ACULAB.COM,
SeongJae Park <sjpark@amazon.de>
Subject: Re: [PATCH v2 2/2] selftests: net: Add FIN_ACK processing order related latency spike test
Date: Sat, 1 Feb 2020 10:20:08 -0800 [thread overview]
Message-ID: <0fc6654c-c938-3920-0097-cddc34474855@gmail.com> (raw)
In-Reply-To: <20200201071859.4231-3-sj38.park@gmail.com>
On 1/31/20 11:18 PM, sj38.park@gmail.com wrote:
> From: SeongJae Park <sjpark@amazon.de>
>
> This commit adds a test for FIN_ACK process races related reconnection
> latency spike issues. The issue has described and solved by the
> previous commit ("tcp: Reduce SYN resend delay if a suspicous ACK is
> received").
>
> The test program is configured with a server and a client process. The
> server creates and binds a socket to a port that dynamically allocated,
> listen on it, and start a infinite loop. Inside the loop, it accepts
> connection, reads 4 bytes from the socket, and closes the connection.
> The client is constructed as an infinite loop. Inside the loop, it
> creates a socket with LINGER and NODELAY option, connect to the server,
> send 4 bytes data, try read some data from server. After the read()
> returns, it measure the latency from the beginning of this loop to this
> point and if the latency is larger than 1 second (spike), print a
> message.
>
> Signed-off-by: SeongJae Park <sjpark@amazon.de>
Reviewed-by: Eric Dumazet <edumazet@google.com>
prev parent reply other threads:[~2020-02-01 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 7:18 [PATCH v2 0/2] Fix reconnection latency caused by FIN/ACK handling race sj38.park
2020-02-01 7:18 ` [PATCH v2 1/2] tcp: Reduce SYN resend delay if a suspicous ACK is received sj38.park
2020-02-01 13:51 ` Neal Cardwell
2020-02-01 14:36 ` SeongJae Park
2020-02-01 14:53 ` [PATCH v2.1 " sj38.park
2020-02-01 18:23 ` Eric Dumazet
2020-02-02 3:40 ` SeongJae Park
2020-02-01 7:18 ` [PATCH v2 2/2] selftests: net: Add FIN_ACK processing order related latency spike test sj38.park
2020-02-01 18:20 ` Eric Dumazet [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fc6654c-c938-3920-0097-cddc34474855@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=aams@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
--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;
as well as URLs for NNTP newsgroup(s).