Hello Ivan, > Overall, the idea of action list indirection sounds good. > But why deprecate the existing indirect action API?
Deprecation is not necessary. If the decision is to keep existing indirect action API, it must be updated to differentiate between action mutable and flow mutable update parameters. > Are there any strong reasons for that? This action > should probably stay. Well, at least, I wouldn't > expect this patch to immediately introduce some > transition period. Let's cross that bridge > when we get there. What do you think? > > Also, what are the target applications/projects to > benefit from the new indirect action list API? > Could you please provide some examples. Or, > alternatively, you could shed light on > which "shapes" of flow rules would > be the primary users of the action. > We have 2 usages for the new indirect list API 1. Create single HW action from input list of RTE actions. For example, MLX5 template API will create single mirror HW action from SAMPLE / JUMP list. 2. METER_MARK init_color and CONNTRACK last_direction parameters are flow mutable, by the actions definitions. However, current indirect action cannot update flow parameters. Regards, Gregory
