hi,
From: Bing Zhao <bi...@nvidia.com>
Sent: Thursday, July 4, 2024 1:26 PM
To: Slava Ovsiienko; dev@dpdk.org; Raslan Darawsheh
Cc: Ori Kam; Dariusz Sosnowski; Suanming Mou; Matan Azrad
Subject: [PATCH v2] net/mlx5: add metadata split for compatibility API
The method will not create any new flow rule implicitly during split
stage, but only generate needed items, actions and attributes based
on the detection.
All the rules will still be created in the flow_hw_list_create().
In the meanwhile, once the mark action is specified in the FDB rule,
a new rule in the NIC Rx will be created to:
1. match the mark value on REG_C_x in FDB and set it into Rx
flow tag field.
2. copy the metadata in REG_C_x' into the REG_B.
If there is no mark, the default rule with only copying metadata
will be hit if there is Queue or RSS action in the NIC Rx rule.
Regarding the NIC Tx, only the metadata is relevant and it will be
copied in NIC Tx from REG_A into some REG_C_x. The current HWS
implementation already has already supported in the default copy
rule or the default SQ miss rule in the NIC Tx root table.
Signed-off-by: Bing Zhao <bi...@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnow...@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
