From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@gmail.com, netdev@vger.kernel.org,
horms@kernel.org, razor@blackwall.org, idosch@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next v3 00/15] ipmr, ip6mr: Allow MC-routing locally-generated MC packets
Date: Wed, 18 Jun 2025 01:41:12 +0000 [thread overview]
Message-ID: <175021087241.3761578.9440566211529797488.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1750113335.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Jun 2025 00:44:08 +0200 you wrote:
> Multicast routing is today handled in the input path. Locally generated MC
> packets don't hit the IPMR code. Thus if a VXLAN remote address is
> multicast, the driver needs to set an OIF during route lookup. In practice
> that means that MC routing configuration needs to be kept in sync with the
> VXLAN FDB and MDB. Ideally, the VXLAN packets would be routed by the MC
> routing code instead.
>
> [...]
Here is the summary with links:
- [net-next,v3,01/15] net: ipv4: Add a flags argument to iptunnel_xmit(), udp_tunnel_xmit_skb()
https://git.kernel.org/netdev/net-next/c/e3411e326fa4
- [net-next,v3,02/15] net: ipv4: ipmr: ipmr_queue_xmit(): Drop local variable `dev'
https://git.kernel.org/netdev/net-next/c/3b7bc938e0ad
- [net-next,v3,03/15] net: ipv4: ipmr: Split ipmr_queue_xmit() in two
https://git.kernel.org/netdev/net-next/c/b2e653bcff0f
- [net-next,v3,04/15] net: ipv4: Add ip_mr_output()
https://git.kernel.org/netdev/net-next/c/35bec72a24ac
- [net-next,v3,05/15] net: ipv6: Make udp_tunnel6_xmit_skb() void
https://git.kernel.org/netdev/net-next/c/6a7d88ca15f7
- [net-next,v3,06/15] net: ipv6: Add a flags argument to ip6tunnel_xmit(), udp_tunnel6_xmit_skb()
https://git.kernel.org/netdev/net-next/c/f78c75d84fe8
- [net-next,v3,07/15] net: ipv6: ip6mr: Fix in/out netdev to pass to the FORWARD chain
https://git.kernel.org/netdev/net-next/c/3365afd3abda
- [net-next,v3,08/15] net: ipv6: ip6mr: Make ip6mr_forward2() void
https://git.kernel.org/netdev/net-next/c/094f39d5e84d
- [net-next,v3,09/15] net: ipv6: ip6mr: Split ip6mr_forward2() in two
https://git.kernel.org/netdev/net-next/c/1b02f4475d29
- [net-next,v3,10/15] net: ipv6: Add ip6_mr_output()
https://git.kernel.org/netdev/net-next/c/96e8f5a9fe2d
- [net-next,v3,11/15] vxlan: Support MC routing in the underlay
https://git.kernel.org/netdev/net-next/c/f8337efa4ff5
- [net-next,v3,12/15] selftests: forwarding: lib: Move smcrouted helpers here
https://git.kernel.org/netdev/net-next/c/2a719b7bacc7
- [net-next,v3,13/15] selftests: net: lib: Add ip_link_has_flag()
https://git.kernel.org/netdev/net-next/c/4baa1d3a5080
- [net-next,v3,14/15] selftests: forwarding: adf_mcd_start(): Allow configuring custom interfaces
https://git.kernel.org/netdev/net-next/c/237f84a6d24a
- [net-next,v3,15/15] selftests: forwarding: Add a test for verifying VXLAN MC underlay
https://git.kernel.org/netdev/net-next/c/e3180379e2df
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:[~2025-06-18 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 22:44 [PATCH net-next v3 00/15] ipmr, ip6mr: Allow MC-routing locally-generated MC packets Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 01/15] net: ipv4: Add a flags argument to iptunnel_xmit(), udp_tunnel_xmit_skb() Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 02/15] net: ipv4: ipmr: ipmr_queue_xmit(): Drop local variable `dev' Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 03/15] net: ipv4: ipmr: Split ipmr_queue_xmit() in two Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 04/15] net: ipv4: Add ip_mr_output() Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 05/15] net: ipv6: Make udp_tunnel6_xmit_skb() void Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 06/15] net: ipv6: Add a flags argument to ip6tunnel_xmit(), udp_tunnel6_xmit_skb() Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 07/15] net: ipv6: ip6mr: Fix in/out netdev to pass to the FORWARD chain Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 08/15] net: ipv6: ip6mr: Make ip6mr_forward2() void Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 09/15] net: ipv6: ip6mr: Split ip6mr_forward2() in two Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 10/15] net: ipv6: Add ip6_mr_output() Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 11/15] vxlan: Support MC routing in the underlay Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 12/15] selftests: forwarding: lib: Move smcrouted helpers here Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 13/15] selftests: net: lib: Add ip_link_has_flag() Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 14/15] selftests: forwarding: adf_mcd_start(): Allow configuring custom interfaces Petr Machata
2025-06-16 22:44 ` [PATCH net-next v3 15/15] selftests: forwarding: Add a test for verifying VXLAN MC underlay Petr Machata
2025-06-18 1:41 ` 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=175021087241.3761578.9440566211529797488.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.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.