From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ivan Malov <ivan.malov@arknetworks.am>, dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@amd.com>, Andy Moreton <andy.moreton@amd.com>
Subject: Re: [PATCH] net/sfc: support packet replay in transfer flows
Date: Sat, 30 Sep 2023 09:31:54 +0300 [thread overview]
Message-ID: <07db6dcf-057e-00bc-54ce-a31bc79ac95e@oktetlabs.ru> (raw)
In-Reply-To: <20230927103605.6022-1-ivan.malov@arknetworks.am>
On 9/27/23 13:36, 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.malov@arknetworks.am>
> Reviewed-by: Andy Moreton <andy.moreton@amd.com>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2023-09-30 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 18:28 [RFC] " Ivan Malov
2023-08-11 12:03 ` [RFC v2] " Ivan Malov
2023-08-31 23:26 ` [RFC v3] " Ivan Malov
2023-09-27 10:36 ` [PATCH] " Ivan Malov
2023-09-29 13:53 ` Ferruh Yigit
2023-09-30 6:31 ` Andrew Rybchenko [this message]
2023-09-30 6:37 ` Ivan Malov
2023-10-02 9:50 ` Ferruh Yigit
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=07db6dcf-057e-00bc-54ce-a31bc79ac95e@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=andy.moreton@amd.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ivan.malov@arknetworks.am \
/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).