From: Neal Cardwell <ncardwell@google.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
sjpark@amazon.com, Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
shuah@kernel.org, Netdev <netdev@vger.kernel.org>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
aams@amazon.com, SeongJae Park <sjpark@amazon.de>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: Re: Re: [PATCH 2/3] tcp: Reduce SYN resend delay if a suspicous ACK is received
Date: Sat, 1 Feb 2020 08:30:08 -0500 [thread overview]
Message-ID: <CADVnQymWFGfX-N_O=p_kqJ2UxQZUDVn1YKrzZ+C+hYWc_OuzMg@mail.gmail.com> (raw)
In-Reply-To: <20200201060843.21626-1-sj38.park@gmail.com>
On Sat, Feb 1, 2020 at 1:08 AM SeongJae Park <sj38.park@gmail.com> wrote:
> RST/ACK is traced if LINGER socket option is applied in the reproduce program,
> and FIN/ACK is traced if it is not applied. LINGER applied version shows the
> spikes more frequently, but the main problem logic has no difference. I
> confirmed this by testing both of the two versions.
>
> In the previous discussion, I showed the LINGER applied trace. However, as
> many other documents are using FIN/ACK, I changed the trace to FIN/ACK version
> in this patchset for better understanding. I will comment that it doesn't
> matter whether it is FIN/ACK or RST/ACK in the next spin.
Great. Thanks for the details!
neal
next prev parent reply other threads:[~2020-02-01 13:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 12:24 [PATCH 0/3] Fix reconnection latency caused by FIN/ACK handling race sjpark
2020-01-31 12:24 ` [PATCH 1/3] net/ipv4/inet_timewait_sock: Fix inconsistent comments sjpark
2020-01-31 14:54 ` Eric Dumazet
2020-01-31 15:09 ` sjpark
2020-01-31 12:24 ` [PATCH 2/3] tcp: Reduce SYN resend delay if a suspicous ACK is received sjpark
2020-01-31 15:01 ` Eric Dumazet
2020-01-31 16:12 ` sjpark
2020-01-31 16:55 ` Eric Dumazet
2020-01-31 17:05 ` sjpark
2020-01-31 17:08 ` Eric Dumazet
2020-01-31 15:10 ` Neal Cardwell
2020-01-31 18:12 ` Eric Dumazet
2020-01-31 22:11 ` Neal Cardwell
2020-01-31 22:17 ` SeongJae Park
2020-02-01 3:55 ` Neal Cardwell
2020-02-01 6:08 ` SeongJae Park
2020-02-01 13:30 ` Neal Cardwell [this message]
2020-01-31 22:53 ` Eric Dumazet
2020-02-03 15:40 ` David Laight
2020-02-03 15:54 ` Eric Dumazet
2020-01-31 12:24 ` [PATCH 3/3] selftests: net: Add FIN_ACK processing order related latency spike test sjpark
2020-01-31 14:56 ` Eric Dumazet
2020-01-31 15:13 ` sjpark
2020-01-31 14:00 ` [PATCH 0/3] Fix reconnection latency caused by FIN/ACK handling race David Laight
2020-01-31 15:05 ` sjpark
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='CADVnQymWFGfX-N_O=p_kqJ2UxQZUDVn1YKrzZ+C+hYWc_OuzMg@mail.gmail.com' \
--to=ncardwell@google.com \
--cc=aams@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.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).