[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADVnQymWFGfX-N_O=p_kqJ2UxQZUDVn1YKrzZ+C+hYWc_OuzMg@mail.gmail.com>
Date: Sat, 1 Feb 2020 08:30:08 -0500
From: Neal Cardwell <ncardwell@...gle.com>
To: SeongJae Park <sj38.park@...il.com>
Cc: Eric Dumazet <eric.dumazet@...il.com>, sjpark@...zon.com,
Eric Dumazet <edumazet@...gle.com>,
David Miller <davem@...emloft.net>, shuah@...nel.org,
Netdev <netdev@...r.kernel.org>, linux-kselftest@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>, aams@...zon.com,
SeongJae Park <sjpark@...zon.de>,
Yuchung Cheng <ycheng@...gle.com>
Subject: Re: Re: Re: [PATCH 2/3] tcp: Reduce SYN resend delay if a suspicous
ACK is received
On Sat, Feb 1, 2020 at 1:08 AM SeongJae Park <sj38.park@...il.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
Powered by blists - more mailing lists