On Mon, 17 Feb 2025 19:21:10 +0200
Gregory Etelson <getel...@nvidia.com> wrote:
> Flow actions parameters in indirect actions list are created as
> read-only and shared between all flows that reference that indirect
> list.
>
> If a flow rule needs to apply rule specific actions list parameters it
> does it with the indirect actions list conf parameter.
>
> The patch allows flow rule to set meter_mark init_color value when
> meter_mark action was created in indirect actions list.
>
> Example:
>
> // create indirect actions list with meter_mark flow action:
> testpmd> flow indirect_action 0 create action_id 10 ingress \
> list actions meter_mark mtr_profile 20 \
> mtr_state 1 mtr_color_mode 1 / end
>
> // create a flow specific meter_mark init_color configuration:
> testpmd> flow indirect_action 0 create action_id 11 flow_conf \
> actions meter_mark_conf mtr_update_init_color red / end
>
> // queue a flow rule with indirect actions list
> // and flow specific configuration:
> testpmd> flow queue 0 create 0 template_table 1 pattern_template 0 \
> actions_template 0 postpone no pattern eth / ipv4 / udp / end \
> actions indirect_list handle 10 conf 11 / \
> jump group 10 / end
>
> Signed-off-by: Gregory Etelson <getel...@nvidia.com>
Looks good, would like a ack from one of the flow maintainers that
looked at the original patch. Those were:
Signed-off-by: Alexander Kozyrev <akozy...@nvidia.com>
Acked-by: Cristian Dumitrescu <cristian.dumitre...@intel.com>
Acked-by: Ori Kam <or...@nvidia.com>
Acked-by: Ajit Khaparde <ajit.khapa...@broadcom.com>
Acked-by: Andrew Rybchenko <andrew.rybche...@oktetlabs.ru>
