From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Vdovin <deliran@verdict.gg>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, davem@davemloft.net,
idosch@idosch.org, edumazet@google.com,
linux-kselftest@vger.kernel.org, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, horms@kernel.org,
gnault@redhat.com
Subject: Re: [PATCH net-next v10] net: ipv4: Cache pmtu for all packet paths if multipath enabled
Date: Tue, 12 Nov 2024 03:40:36 +0000 [thread overview]
Message-ID: <173138283699.71105.6903753755022416779.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241108093427.317942-1-deliran@verdict.gg>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 8 Nov 2024 09:34:24 +0000 you wrote:
> Check number of paths by fib_info_num_path(),
> and update_or_create_fnhe() for every path.
> Problem is that pmtu is cached only for the oif
> that has received icmp message "need to frag",
> other oifs will still try to use "default" iface mtu.
>
> An example topology showing the problem:
>
> [...]
Here is the summary with links:
- [net-next,v10] net: ipv4: Cache pmtu for all packet paths if multipath enabled
https://git.kernel.org/netdev/net-next/c/7d3f3b4367f3
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:[~2024-11-12 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 9:34 [PATCH net-next v10] net: ipv4: Cache pmtu for all packet paths if multipath enabled Vladimir Vdovin
2024-11-10 11:28 ` Ido Schimmel
2024-11-12 3: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=173138283699.71105.6903753755022416779.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=deliran@verdict.gg \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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.