On 9/27/2023 11:36 AM, Ivan Malov wrote: > Packet replay enables users to leverage multiple counters in > one flow and allows to request delivery to multiple ports. > > A given flow rule may use either one inline count action > and multiple indirect counters or just multiple indirect > counters. The inline count action (if any) must come > before the first delivery action or before the first > indirect count action, whichever comes earlier. > > These are some testpmd examples of supported > multi-count and mirroring use cases: > > flow create 0 transfer pattern represented_port ethdev_port_id is 0 / end \ > actions port_representor port_id 0 / port_representor port_id 1 / end > > or > > flow indirect_action 0 create action_id 239 transfer action count / end > > flow create 0 transfer pattern represented_port ethdev_port_id is 0 / end \ > actions count / port_representor port_id 0 / indirect 239 / \ > port_representor port_id 1 / end > > or > > flow indirect_action 0 create action_id 239 transfer action count / end > > flow create 0 transfer pattern represented_port ethdev_port_id is 0 / end \ > actions indirect 239 / port_representor port_id 0 / indirect 239 / \ > port_representor port_id 1 / end > > and the likes. > > Signed-off-by: Ivan Malov <ivan.ma...@arknetworks.am> > Reviewed-by: Andy Moreton <andy.more...@amd.com> >
Hi Andrew, Reminder of this patch waiting for review.
