From: Jakub Kicinski <kuba@kernel.org>
To: sj38.park@gmail.com
Cc: edumazet@google.com, David.Laight@aculab.com, aams@amazon.com,
davem@davemloft.net, eric.dumazet@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, ncardwell@google.com,
shuah@kernel.org, sjpark@amazon.de
Subject: Re: [PATCH v3 0/2] Fix reconnection latency caused by FIN/ACK handling race
Date: Sun, 2 Feb 2020 13:46:52 -0800 [thread overview]
Message-ID: <20200202134652.0e89ce89@cakuba.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20200202033827.16304-1-sj38.park@gmail.com>
On Sun, 2 Feb 2020 03:38:25 +0000, sj38.park@gmail.com wrote:
> The first patch fixes the problem by adjusting the first resend delay of
> the SYN in the case. The second one adds a user space test to reproduce
> this problem.
>
> The patches are based on the v5.5. You can also clone the complete git
> tree:
>
> $ git clone git://github.com/sjp38/linux -b patches/finack_lat/v3
>
> The web is also available:
> https://github.com/sjp38/linux/tree/patches/finack_lat/v3
Applied to net, thank you!
In the future there is no need to duplicate the info from commit
messages in the cover letter.
next prev parent reply other threads:[~2020-02-02 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 3:38 [PATCH v3 0/2] Fix reconnection latency caused by FIN/ACK handling race sj38.park
2020-02-02 3:38 ` [PATCH v3 1/2] tcp: Reduce SYN resend delay if a suspicous ACK is received sj38.park
2020-02-02 3:38 ` [PATCH v3 2/2] selftests: net: Add FIN_ACK processing order related latency spike test sj38.park
2020-02-02 21:46 ` Jakub Kicinski [this message]
2020-02-02 22:08 ` Re: [PATCH v3 0/2] Fix reconnection latency caused by FIN/ACK handling race SeongJae Park
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=20200202134652.0e89ce89@cakuba.hsd1.ca.comcast.net \
--to=kuba@kernel.org \
--cc=David.Laight@aculab.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=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
/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).