[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c5c69f8-b7c1-6de7-e22a-5bb267f5562d@gmail.com>
Date: Fri, 23 Feb 2024 13:44:23 +0000
From: Edward Cree <ecree.xilinx@...il.com>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Jiri Pirko <jiri@...nulli.us>, Ahmed Zaki <ahmed.zaki@...el.com>,
stephen@...workplumber.org, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, corbet@....net, xiyou.wangcong@...il.com,
netdev@...r.kernel.org, "Chittim, Madhu" <madhu.chittim@...el.com>,
"Samudrala, Sridhar" <sridhar.samudrala@...el.com>,
amritha.nambiar@...el.com, Jan Sokolowski <jan.sokolowski@...el.com>,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [RFC]: raw packet filtering via tc-flower
On 23/02/2024 13:32, Jamal Hadi Salim wrote:
> u32 has a DSL that deals with parsing as well, which includes dealing
> with variable packet offsets etc. That is a necessary ingredient if
> you want to do pragmatic parsing (example how do you point to TCP
> ports if the IP header has options etc).
My understanding (Ahmed can correct me) is that the proposed raw
filtering here would not support variable packet offsets at all.
That is precisely why I consider it a narrow hack for specialised
use-cases and thus oppose its addition to cls_flower.
Powered by blists - more mailing lists