netdev - Re: [PATCH net-next 0/2] tcp: change pingpong to 3 in delayed ack logic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20190127.132956.1159263225785994001.davem@davemloft.net>
Date:   Sun, 27 Jan 2019 13:29:56 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     weiwan@...gle.com
Cc:     netdev@...r.kernel.org, ycheng@...gle.com, ncardwell@...gle.com,
        edumazet@...gle.com
Subject: Re: [PATCH net-next 0/2] tcp: change pingpong to 3 in delayed ack
 logic

From: Wei Wang <weiwan@...gle.com>
Date: Fri, 25 Jan 2019 10:53:18 -0800

> TCP receiver today tries not to delay the ACKs to speed up the initial
> slow start (a.k.a QUICK ACK mechanism). However the previous design
> does not work well with modern TCP applications that starts with an
> application-level handshake. For example, a HTTPs server often
> receives the SSL hello and responds right away which triggers the TCP
> stack to stop the quick ack and start delaying the ACKs based only one
> instance of ping-pong. This patchset changes the threshold from 1 to 3
> ping-pong transactions, so that we only start to delay the acks after
> the receiver responds data quickly three times.

Series applied, thanks.