From: patchwork-bot+netdevbpf@kernel.org
To: Omar Ramadan <omar@blockcast.net>
Cc: ap420073@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
shuah@kernel.org, horms@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] amt: mark relay data as a UDP tunnel packet, with a selftest
Date: Thu, 08 Oct 2026 02:10:09 +0000 [thread overview]
Message-ID: <179142540927.3771647.9405925708782465037.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261004161200.27196-1-omar@blockcast.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 4 Oct 2026 19:11:58 +0300 you wrote:
> amt_send_multicast_data() never calls udp_tunnel_handle_offloads(),
> unlike other UDP tunnels. With tx checksum offload on the amt device (off
> by default), a UDP_SEGMENT burst through the relay is dropped before
> patch 1 and delivered after it. Patch 2 adds the selftest.
>
> This follows Eric Dumazet's suggestion on my withdrawn [PATCH net] "amt:
> do not offer software GSO on the amt device":
> https://lore.kernel.org/all/20260928181554.85766-1-omar@blockcast.net/
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] amt: mark relay data as a UDP tunnel packet before sending it
https://git.kernel.org/netdev/net-next/c/47bb8dfbe1d2
- [net-next,v3,2/2] selftests: net: add an amt test for UDP_SEGMENT through the relay
(no matching commit)
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-10-08 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 16:11 Omar Ramadan
2026-10-04 16:11 ` [PATCH net-next v3 1/2] amt: mark relay data as a UDP tunnel packet before sending it Omar Ramadan
2026-10-04 16:12 ` [PATCH net-next v3 2/2] selftests: net: add an amt test for UDP_SEGMENT through the relay Omar Ramadan
2026-10-08 2:08 ` Jakub Kicinski
2026-10-08 2:10 ` 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=179142540927.3771647.9405925708782465037.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omar@blockcast.net \
--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
all inboxes | Powered by JetHome®