Thread (8 messages) 8 messages, 4 authors, 2024-06-06

Re: [PATCH net-next v4 0/2] net: allow dissecting/matching tunnel control flags

From: patchwork-bot+netdevbpf@kernel.org
Date: 2024-06-04 09:50:30

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni [off-list ref]:

On Thu, 30 May 2024 19:08:33 +0200 you wrote:
Ilya says: "for correct matching on decapsulated packets, we should match
on not only tunnel id and headers, but also on tunnel configuration flags
like TUNNEL_NO_CSUM and TUNNEL_DONT_FRAGMENT. This is done to distinguish
similar tunnels with slightly different configs. And it is important since
tunnel configuration is flow based, i.e. can be different for every packet,
even though the main tunnel port is the same."

[...]
Here is the summary with links:
  - [net-next,v4,1/2] flow_dissector: add support for tunnel control flags
    https://git.kernel.org/netdev/net-next/c/668b6a2ef832
  - [net-next,v4,2/2] net/sched: cls_flower: add support for matching tunnel control flags
    https://git.kernel.org/netdev/net-next/c/1d17568e74de

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help