[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<171749463020.15457.3342638051928140051.git-patchwork-notify@kernel.org>
Date: Tue, 04 Jun 2024 09:50:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Davide Caratti <dcaratti@...hat.com>
Cc: davem@...emloft.net, edumazet@...gle.com, i.maximets@....org,
jhs@...atatu.com, jiri@...nulli.us, kuba@...nel.org, lucien.xin@...il.com,
marcelo.leitner@...il.com, netdev@...r.kernel.org, pabeni@...hat.com,
xiyou.wangcong@...il.com, echaudro@...hat.com
Subject: Re: [PATCH net-next v4 0/2] net: allow dissecting/matching tunnel control
flags
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:
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
Powered by blists - more mailing lists