From: Yongjian Wang via B4 Relay <devnull+echoowall.gmail.com@kernel.org>
To: corbet@lwn.net, edumazet@kernel.org, davem@davemloft.net,
kuba@kernel.org, shuah@kernel.org, pabeni@redhat.com
Cc: Yongjian Wang <echoowall@gmail.com>,
rdunlap@infradead.org, linux-doc@vger.kernel.org,
horms@kernel.org, ncardwell@google.com, kuniyu@google.com,
skhan@linuxfoundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH net-next v2 1/2] tcp: document black hole detection for tcp_mtu_probing
Date: Wed, 18 Nov 2026 16:10:52 +0800 [thread overview]
Message-ID: <20261118-tcp-mtu-probing-doc-v1-v2-1-e795f20b8cfe@gmail.com> (raw)
In-Reply-To: <20261118-tcp-mtu-probing-doc-v1-v2-0-e795f20b8cfe@gmail.com>
From: Yongjian Wang <echoowall@gmail.com>
ip-sysctl.rst says that tcp_mtu_probing=1 enables MTU probing once an
ICMP black hole is detected, but not when that happens or what TCP
does then.
Describe both, as implemented in tcp_write_timeout() and
tcp_mtu_probing(). Also add the missing defaults of tcp_mtu_probing
and tcp_base_mss.
Signed-off-by: Yongjian Wang <echoowall@gmail.com>
Reviewed-by: Eric Dumazet <edumazet@kernel.org>
---
Documentation/networking/ip-sysctl.rst | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
index 0b7bfbd98a92..6ac8b3fb9aae 100644
--- a/Documentation/networking/ip-sysctl.rst
+++ b/Documentation/networking/ip-sysctl.rst
@@ -412,6 +412,8 @@ tcp_base_mss - INTEGER
Path MTU discovery (MTU probing). If MTU probing is enabled,
this is the initial MSS used by the connection.
+ Default: 1024
+
tcp_mtu_probe_floor - INTEGER
If MTU probing is enabled this caps the minimum MSS used for search_low
for the connection.
@@ -711,6 +713,25 @@ tcp_mtu_probing - INTEGER
- 1 - Disabled by default, enabled when an ICMP black hole detected
- 2 - Always enabled, use initial MSS of tcp_base_mss.
+ A black hole is detected when the retransmission timer fires after
+ the handshake and retransmissions have stayed unacknowledged for as
+ long as tcp_retries1 retransmissions would take with an RTO starting
+ at 200 ms and doubling each time, which is 3 seconds with the
+ default tcp_retries1. This time is counted from the first
+ retransmission and only checked when the timer fires, so a flow
+ with a 200 ms RTO detects the black hole at the fifth timeout,
+ about 6 seconds after the original transmission.
+
+ With value 1, the first detection enables MTU probing and lowers
+ the MSS to tcp_base_mss if it is larger. From then on, and from the
+ first detection with value 2, each further retransmission timeout
+ lowers search_low to half its MSS, keeping it at most tcp_base_mss
+ and at least tcp_mtu_probe_floor and tcp_min_snd_mss, and lowers the
+ MSS to match if it is larger. Once MTU probing is enabled, the
+ connection also probes for a larger MSS, as with value 2.
+
+ Default: 0
+
tcp_probe_interval - UNSIGNED INTEGER
Controls how often to start TCP Packetization-Layer Path MTU
Discovery reprobe. The default is reprobing every 10 minutes as
--
Git-157)
next prev parent reply other threads:[~2026-11-18 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 8:10 [PATCH net-next v2 0/2] tcp: document and test MTU probing black hole fallback Yongjian Wang via B4 Relay
2026-11-18 8:10 ` Yongjian Wang via B4 Relay [this message]
2026-11-18 8:10 ` [PATCH net-next v2 2/2] selftests/net: packetdrill: test tcp_mtu_probe_floor Yongjian Wang via B4 Relay
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=20261118-tcp-mtu-probing-doc-v1-v2-1-e795f20b8cfe@gmail.com \
--to=devnull+echoowall.gmail.com@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=echoowall@gmail.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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
all inboxes | Powered by JetHome®