[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169828382629.14693.2027988602080029983.git-patchwork-notify@kernel.org>
Date: Thu, 26 Oct 2023 01:30:26 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Yan Zhai <yan@...udflare.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, dsahern@...nel.org,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
ayal@...dia.com, tariqt@...dia.com, linux-kernel@...r.kernel.org,
kernel-team@...udflare.com, fw@...len.de,
willemdebruijn.kernel@...il.com, alexander.duyck@...il.com
Subject: Re: [PATCH v5 net-next 0/3] ipv6: avoid atomic fragment on GSO output
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 24 Oct 2023 07:26:28 -0700 you wrote:
> When the ipv6 stack output a GSO packet, if its gso_size is larger than
> dst MTU, then all segments would be fragmented. However, it is possible
> for a GSO packet to have a trailing segment with smaller actual size
> than both gso_size as well as the MTU, which leads to an "atomic
> fragment". Atomic fragments are considered harmful in RFC-8021. An
> Existing report from APNIC also shows that atomic fragments are more
> likely to be dropped even it is equivalent to a no-op [1].
>
> [...]
Here is the summary with links:
- [v5,net-next,1/3] ipv6: drop feature RTAX_FEATURE_ALLFRAG
https://git.kernel.org/netdev/net-next/c/e57a34478586
- [v5,net-next,2/3] ipv6: refactor ip6_finish_output for GSO handling
https://git.kernel.org/netdev/net-next/c/1f7ec1b3721d
- [v5,net-next,3/3] ipv6: avoid atomic fragment on GSO packets
https://git.kernel.org/netdev/net-next/c/03d6c848bfb4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists