From: patchwork-bot+netdevbpf@kernel.org
To: Neil Spring <ntspring@meta.com>
Cc: netdev@vger.kernel.org, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
kuba@kernel.org, dsahern@kernel.org, pabeni@redhat.com,
horms@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org,
martin.lau@linux.dev, daniel@iogearbox.net
Subject: Re: [PATCH net-next v14 0/2] tcp: rehash onto different local ECMP path on retransmit timeout
Date: Mon, 15 Jun 2026 23:40:26 +0000 [thread overview]
Message-ID: <178156682638.339383.5955465321121394941.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260615042158.1600746-1-ntspring@meta.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 14 Jun 2026 21:21:56 -0700 you wrote:
> Currently sk_rethink_txhash() re-rolls the socket's txhash on RTO,
> PLB, and spurious-retransmission events, but the new hash is not
> propagated into the IPv6 ECMP path selection. The cached
> route is reused and fib6_select_path() is never re-invoked, so
> the connection uses the same local ECMP decision.
>
> This series adds the two missing pieces:
>
> [...]
Here is the summary with links:
- [v14,1/2] tcp: rehash onto different local ECMP path on retransmit timeout
https://git.kernel.org/netdev/net-next/c/658eb696544c
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-06-15 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 4:21 [PATCH net-next v14 0/2] tcp: rehash onto different local ECMP path on retransmit timeout Neil Spring
2026-06-15 4:21 ` [PATCH v14 1/2] " Neil Spring
2026-06-15 16:55 ` Eric Dumazet
2026-06-15 4:21 ` [PATCH v14] selftests: net: add local ECMP rehash test Neil Spring
2026-06-15 23:40 ` patchwork-bot+netdevbpf
2026-06-15 23:40 ` 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=178156682638.339383.5955465321121394941.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ntspring@meta.com \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox