Hi Ran, On 2026-03-13T00:25:53+0200, Ran Benita wrote: > TCP_DEFER_ACCEPT has an interesting little-known effect on client > sockets. I don't think it's very useful but should still be documented. > > See here for reference: > > > Signed-off-by: Ran Benita Thanks! Please see some comments below. Have a lovely night! Alex > --- > man/man7/tcp.7 | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/man/man7/tcp.7 b/man/man7/tcp.7 > index adfd6623e..85f6c631c 100644 > --- a/man/man7/tcp.7 > +++ b/man/man7/tcp.7 > @@ -1091,6 +1091,11 @@ Allow a listener to be awakened only when data arrives on the socket. > Takes an integer value (seconds), this can > bound the maximum number of attempts TCP will make to > complete the connection. > +.IP > +On a client socket, if non-zero, delays sending the final ACK of the three-way s/non-zero/nonzero/ $ grep -rho 'non[^ ]*zero' | sort | uniq -c 72 non-zero 4 non\-zero 2119 nonzero 3 nonzero non-zero 2 nonzero/non-zero 2 nonzero\h'|\n[3cl1]u'non-zero > +handshake until the socket has data to send, in which case the ACK is > +piggybacked on the first data segment, or a delayed-ACK timeout is reached. Please use semantic newlines. See man-pages(7): $ MANWIDTH=72 man man-pages | awk '/Use semantic newlines/,/^$/' Use semantic newlines In the source of a manual page, new sentences should be started on new lines, long sentences should be split into lines at clause breaks (commas, semicolons, colons, and so on), and long clauses should be split at phrase boundaries. This convention, sometimes known as "semantic newlines", makes it easier to see the effect of patches, which often operate at the level of individual sentences, clauses, or phrases. > +.IP > This option should not be used in code intended to be portable. > .TP > .BR TCP_INFO " (since Linux 2.4)" > -- > 2.53.0 > --