From: Jan Viktorin <viktorin@cesnet.cz>
To: dev@dpdk.org
Subject: [dpdk-dev] Duplicating traffic with RTE Flow
Date: Fri, 18 Sep 2020 14:56:18 +0200 [thread overview]
Message-ID: <20200918145618.052ee504@tanguero.localdomain> (raw)
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://doc.dpdk.org/guides/prog_guide/rte_flow.html#table-rte-flow-redirect-queue-5-3
next reply other threads:[~2020-09-18 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 12:56 Jan Viktorin [this message]
2020-09-18 14:23 ` Asaf Penso
2020-09-21 20:03 ` Jan Viktorin
2020-09-23 2:28 ` Jiawei(Jonny) Wang
2020-09-23 8:29 ` Jan Viktorin
2020-09-27 6:33 ` Jiawei(Jonny) Wang
2021-03-01 12:21 ` Jan Viktorin
2021-03-01 14:34 ` Slava Ovsiienko
2021-03-01 14:43 ` Jan Viktorin
2021-03-11 2:11 ` Jiawei(Jonny) Wang
2021-03-11 16:32 ` Jan Viktorin
2021-03-12 9:32 ` Jiawei(Jonny) Wang
2021-03-15 13:22 ` Jan Viktorin
2021-03-15 17:57 ` Jan Viktorin
2021-03-16 4:00 ` Jiawei(Jonny) Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200918145618.052ee504@tanguero.localdomain \
--to=viktorin@cesnet.cz \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).