Hello Jan, You can have a look in series [1] where we propose to add APIs to DPDK20.11 for both mirroring and sampling for packets, with additional actions of the different traffic.
[1] http://patches.dpdk.org/project/dpdk/list/?series=12045 Regards, Asaf Penso >-----Original Message----- >From: dev <dev-boun...@dpdk.org> On Behalf Of Jan Viktorin >Sent: Friday, September 18, 2020 3:56 PM >To: dev@dpdk.org >Subject: [dpdk-dev] Duplicating traffic with RTE Flow > >Hello all, > >we are looking for a way to duplicate ingress traffic in hardware. > >There is an example in [1] suggesting to insert two fate actions into the RTE >Flow >actions array like: > > flow create 0 ingress pattern end \ > actions queue index 0 / void / queue index 1 / end > >But our experience is that PMDs reject two fate actions (tried with mlx5). >Another >similar approach would be to deliver every single packet into two virtual >functions: > > flow create 0 ingress pattern end \ > actions vf index 0 / vf index 1 / end > >Third possibility was to use passthru: > > flow create 0 ingress pattern end \ > actions passthru / vf index 0 / end > flow create 0 ingress pattern end \ > actions vf index 1 / end > >Again, tried on mlx5 and it does not support the passthru. > >Last idea was to use isolate with passthru (to deliver both to DPDK application >and to the kernel) but again there was no support on mlx5 for passthru... > > flow isolate 0 true > flow create 0 ingress pattern end actions passthru / rss end / end > >Is there any other possibility or PMD+NIC that is known to solve such issue? > >Thanks >Jan Viktorin > >[1] >https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.dpdk >.org%2Fguides%2Fprog_guide%2Frte_flow.html%23table-rte-flow-redirect- >queue-5- >3&data=02%7C01%7Casafp%40nvidia.com%7C1a46005bec5245e729e708d >85bd24caf%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C6373603060 >73519816&sdata=EOF%2Fz62crvBZK8rwzwKIWxj5cVlfPVnU3FLmcL9X2w0%3 >D&reserved=0
