public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Ran Benita <ran@unusedvar.com>
Cc: linux-man@vger.kernel.org
Subject: Re: man/man7/tcp.7: Document effect of TCP_DEFER_ACCEPT on clientsocket
Date: Fri, 13 Mar 2026 00:38:52 +0100	[thread overview]
Message-ID: <abNNg0RZSfQIPhAp@devuan> (raw)
In-Reply-To: <18e37f7f-21e9-4e8d-bef3-2adde5980bc2@app.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]

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:
> <https://elixir.bootlin.com/linux/v6.19.6/source/net/ipv4/tcp_input.c#L6781-L6796>
> 
> Signed-off-by: Ran Benita <ran@unusedvar.com>

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
> 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-03-12 23:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12 22:25 man/man7/tcp.7: Document effect of TCP_DEFER_ACCEPT on clientsocket Ran Benita
2026-03-12 23:38 ` Alejandro Colomar [this message]
2026-03-13  9:26 ` [PATCH v2] man/man7/tcp.7: Document effect of TCP_DEFER_ACCEPT on client socket Ran Benita
2026-03-16  0:10   ` Alejandro Colomar

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=abNNg0RZSfQIPhAp@devuan \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=ran@unusedvar.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