From: patchwork-bot+netdevbpf@kernel.org
To: Esko Mobius <echoowall@gmail.com>
Cc: pabeni@redhat.com, kuba@kernel.org, shuah@kernel.org,
edumazet@kernel.org, horms@kernel.org, kuniyu@google.com,
ncardwell@google.com, davem@davemloft.net,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, panweiping3@gmail.com
Subject: Re: [PATCH net-next v4 0/4] tcp: fix tcp_base_mss on passive connections and test MTU probing
Date: Mon, 16 Nov 2026 23:20:07 +0000 [thread overview]
Message-ID: <179487120703.232553.15818759103747706687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111-mtu-probing-series-v4-0-6f2e484ca8ea@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Nov 2026 00:45:54 +0800 you wrote:
> With tcp_mtu_probing=2, passive TCP connections can start at the full
> MSS because they sync MSS before initializing MTU probing. Patch 1
> moves initialization next to the existing MSS sync in the passive
> paths and in the active SYN-ACK path. Patch 2 adds a regression test.
>
> Patches 3 and 4 add coverage for black hole detection and the MTU
> search on active connections.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/4] tcp: initialize MTU probing before syncing MSS at connection setup
https://git.kernel.org/netdev/net-next/c/6bde47e9c04a
- [net-next,v4,2/4] selftests/net: packetdrill: test tcp_base_mss on passive connections
https://git.kernel.org/netdev/net-next/c/beb698cfc334
- [net-next,v4,3/4] selftests/net: packetdrill: add TCP black hole detection tests
https://git.kernel.org/netdev/net-next/c/8a83f21ad75d
- [net-next,v4,4/4] selftests/net: packetdrill: add TCP MTU probing test
https://git.kernel.org/netdev/net-next/c/c95a797b0253
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-16 23:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:45 [PATCH net-next v4 0/4] tcp: fix tcp_base_mss on passive connections and test MTU probing Yongjian Wang via B4 Relay
2026-11-10 16:45 ` Yongjian Wang
2026-11-10 16:45 ` [PATCH net-next v4 1/4] tcp: initialize MTU probing before syncing MSS at connection setup Yongjian Wang via B4 Relay
2026-11-10 16:45 ` Yongjian Wang
2026-11-14 16:11 ` Neal Cardwell
2026-11-10 16:45 ` [PATCH net-next v4 2/4] selftests/net: packetdrill: test tcp_base_mss on passive connections Yongjian Wang via B4 Relay
2026-11-10 16:45 ` Yongjian Wang
2026-11-14 6:14 ` Kuniyuki Iwashima
2026-11-14 16:12 ` Neal Cardwell
2026-11-10 16:45 ` [PATCH net-next v4 3/4] selftests/net: packetdrill: add TCP black hole detection tests Yongjian Wang via B4 Relay
2026-11-10 16:45 ` Yongjian Wang
2026-11-14 6:18 ` Kuniyuki Iwashima
2026-11-14 16:13 ` Neal Cardwell
2026-11-10 16:45 ` [PATCH net-next v4 4/4] selftests/net: packetdrill: add TCP MTU probing test Yongjian Wang via B4 Relay
2026-11-10 16:45 ` Yongjian Wang
2026-11-14 6:22 ` Kuniyuki Iwashima
2026-11-14 16:14 ` Neal Cardwell
2026-11-16 23:20 ` patchwork-bot+netdevbpf [this message]
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=179487120703.232553.15818759103747706687.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=panweiping3@gmail.com \
--cc=shuah@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.