[PATCH v2] net/ice: fix how ice driver handles flows
Bruce Richardson
bruce.richardson at intel.com
Thu Jan 30 18:54:43 CET 2025
On Thu, Jan 30, 2025 at 04:14:42PM +0000, Vladimir Medvedkin wrote:
> Currently ICE PMD uses group attribute to select the appropriate HW engine
> to offload the flow. This behavior violates the rte_flow API, existing
> documentation/examples, and reveals hardware specific details.
>
> This patch eliminates the use of the group attribute and runs each engine
> parser in the order they work in the HW pipeline.
>
> Fixes: 9c5f0070fa3f ("net/ice: map group to pipeline stage")
> Cc: qi.z.zhang at intel.com
> Cc: stable at dpdk.org
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin at intel.com>
Thanks, this seems a great idea, to automatically put the flow in place.
Question: is there ever a scenario where a user may need, or want, to
override the automatic choice made here? Or is it just the case that once
the flow is installed, it works the same whatever group it's added into?
I would assume the latter, but just want to confirm.
/Bruce
More information about the dev
mailing list