From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Gregory Etelson <getelson@nvidia.com>, dev@dpdk.org
Cc: mkashani@nvidia.com, Ori Kam <orika@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Subject: Re: [PATCH] app/testpmd: add size parameter to raw_encap action
Date: Thu, 8 Feb 2024 22:50:57 +0000 [thread overview]
Message-ID: <620594cb-b92e-415f-8f17-ba668251015f@amd.com> (raw)
In-Reply-To: <20231026073047.300888-1-getelson@nvidia.com>
On 10/26/2023 8:30 AM, Gregory Etelson wrote:
> Testpmd always provides RAW_ENCAP flow action configuration with
> encap buffer and the buffer size.
> That implementation does not allow to create non-masked raw_encap
> action in the template API actions template.
>
> The patch adds the `size` parameter to testpmd `raw_encap` action
> configuration.
> Testpmd can create non-masked raw-encap action template and specify
> encap buffer during flow creation.
>
> Example:
>
> # total data size is 50
> testpmd> set raw_encap 0 \
> eth src is 11:22:33:44:55:66 dst is aa:bb:cc:dd:01:aa / \
> ipv4 src is 31.31.31.31 dst is 63.63.63.1 / udp src is 1 / \
> vxlan vni is 1 / end_set
>
> testpmd> flow actions_template 0 create ingress \
> actions_template_id 50 \
> template raw_encap size 50 / jump / end \
> mask raw_encap size 50 / jump / end \
>
> tstpmd> flow queue 0 create 0 template_table 0 \
> pattern_template 0 actions_template 0 postpone no \
> pattern ... end \
> actions raw_encap index 0 / jump group 1 / end
>
> The new `size` parameter is mutually exclusive with the existing
> `index` parameter.
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
>
Hi Ori, Can you please support reviewing this patch?
next prev parent reply other threads:[~2024-02-08 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 7:30 Gregory Etelson
2024-02-08 22:50 ` Ferruh Yigit [this message]
2024-02-09 11:03 ` Dariusz Sosnowski
2024-02-09 13:43 ` Dariusz Sosnowski
2024-02-09 13:55 ` Ferruh Yigit
2024-02-09 14:01 ` Gregory Etelson
2024-02-09 15:00 ` Ferruh Yigit
2024-02-09 16:00 ` Dariusz Sosnowski
2024-02-09 16:32 ` 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=620594cb-b92e-415f-8f17-ba668251015f@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=yuying.zhang@intel.com \
/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).