From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: [PATCH v4] net/mlx5: add indirect encap decap support
Date: Mon, 30 Oct 2023 07:22:49 +0000 [thread overview]
Message-ID: <MN0PR12MB6056C6FC629AE6EDE1568F24CFA1A@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231029153022.284208-1-rongweil@nvidia.com>
Hi,
> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Sunday, October 29, 2023 5:30 PM
> To: dev@dpdk.org; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> <thomas@monjalon.net>
> Subject: [PATCH v4] net/mlx5: add indirect encap decap support
>
> Support the raw_encap/decap combinations in the indirect action list, and
> translates to 4 types of underlayer tunnel operations:
> 1. Layer 2 encapsulation like VxLAN.
> 2. Layer 2 decapsulation like VxLAN.
> 3. Layer 3 encapsulation like GRE.
> 4. Layer 3 decapsulation like GRE.
>
> Each indirect action list has a unique handle ID and stands for different tunnel
> operations. The operation is shared globally with fixed patterns. It means there
> is no configuration associated with each handle ID and conf pointer should be
> NULL always no matter in the action template or flow rules.
>
> If the handle ID mask in the action template is NULL, each flow rule can take its
> own indirect handle, otherwise, the ID in action template is used for all rules.
> The handle ID used in the flow rules must be the same type as the one in the
> action template.
>
> Testpmd cli example:
>
> flow indirect_action 0 create action_id 10 transfer list actions raw_decap index
> 1 / raw_encap index 2 / end
>
> flow pattern_template 0 create transfer pattern_template_id 1 template eth /
> ipv4 / udp / end
>
> flow actions_template 0 create transfer actions_template_id 1 template
> indirect_list handle 10 / jump / end mask indirect_list / jump / end
>
> flow template_table 0 create table_id 1 group 1 priority 0 transfer
> rules_number 64 pattern_template 1 actions_template 1
>
> flow queue 0 create 0 template_table 1 pattern_template 0 actions_template
> 0 postpone no pattern eth / ipv4 / udp / end actions indirect_list handle 11 /
> jump group 10 / end
>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> Acked-by: Suanming Mou <suanmingm@nvidia.com>
>
> v4, v3: add macro to fix build failure
> v2: rebase
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-10-30 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 2:26 [PATCH v1] " Rongwei Liu
2023-10-29 10:09 ` [PATCH v2] " Rongwei Liu
2023-10-29 12:53 ` [PATCH v3] " Rongwei Liu
2023-10-29 14:32 ` Raslan Darawsheh
2023-10-29 14:34 ` Raslan Darawsheh
2023-10-29 15:30 ` [PATCH v4] " Rongwei Liu
2023-10-30 7:22 ` Raslan Darawsheh [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=MN0PR12MB6056C6FC629AE6EDE1568F24CFA1A@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).