Hi, > -----Original Message----- > From: Sean Zhang <xiazh...@nvidia.com> > Sent: Tuesday, October 25, 2022 9:31 AM > To: NBU-Contact-Thomas Monjalon (EXTERNAL) <tho...@monjalon.net>; > Matan Azrad <ma...@nvidia.com>; Slava Ovsiienko > <viachesl...@nvidia.com> > Cc: dev@dpdk.org > Subject: [v4] net/mlx5: support matching flow on port representor ID > > 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> > --- > The depending patches as below: > > [1] http://patches.dpdk.org/project/dpdk/cover/20220930125315.5079-1- > suanmi...@nvidia.com > --- > v4 - update the commit title > v3 - rebase to the latest version > v2 - commit message updated and add missing feature in doc > ---
Patch applied to next-net-mlx, Kindest regards, Raslan Darawsheh
