From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ivan Malov <ivan.malov@arknetworks.am>,
dev@dpdk.org
Cc: Andy Moreton <andy.moreton@amd.com>
Subject: Re: [PATCH] net/sfc: support packet replay in transfer flows
Date: Mon, 2 Oct 2023 10:50:39 +0100 [thread overview]
Message-ID: <3536b38a-34f2-4aa8-a189-bcc7b091a6e6@amd.com> (raw)
In-Reply-To: <07db6dcf-057e-00bc-54ce-a31bc79ac95e@oktetlabs.ru>
On 9/30/2023 7:31 AM, Andrew Rybchenko wrote:
> 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>
>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-10-02 9:50 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
2023-09-30 6:37 ` Ivan Malov
2023-10-02 9:50 ` Ferruh Yigit [this message]
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=3536b38a-34f2-4aa8-a189-bcc7b091a6e6@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=andy.moreton@amd.com \
--cc=dev@dpdk.org \
--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).