As title, I suggest: net/mlx5: support matching flow on port representor ID
24/10/2022 03:48, Sean Zhang: > Add support for port_representor item, it will match on traffic > originated from representor port specified in the pattern. This item > is supported in FDB steering domain only (in the flow with transfer > attribute). > > For example, below flow will redirect the destination of traffic from > ethdev 1 to ethdev 2. > > testpmd> ... pattern eth / port_representor port_id is 1 / end actions > represented_port ethdev_port_id 2 / ... > > To handle abovementioned item, Tx queue matching is added in the driver, > and the flow will be expanded to number of the Tx queues. If the spec of > port_representor is NULL, the flow will not be expanded and match on > traffic from any representor port. > > Signed-off-by: Sean Zhang <xiazh...@nvidia.com> > Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com>
