From: Ori Kam <orika@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Maayan Kashani <mkashani@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>
Subject: RE: [PATCH v3] net/mlx5: reuse reformat and modify header actions in a table
Date: Sun, 29 Oct 2023 15:51:43 +0000 [thread overview]
Message-ID: <MW2PR12MB46667F415C6DC83C679170E3D6A2A@MW2PR12MB4666.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230924094124.752639-1-getelson@nvidia.com>
> -----Original Message-----
> From: Gregory Etelson <getelson@nvidia.com>
> Sent: Sunday, September 24, 2023 12:41 PM
>
> If application defined several actions templates with non-shared
> reformat or modify headers actions AND used these templates to create
> a table, HWS could share reformat or modify headers resources,
> instead of creating a resource for each action template.
>
> The patch activates HWS code in a way that provides reformat or
> modify header resources sharing.
>
> The patch updates modify field and raw encap template actions
> validations:
> - modify field does not allow empty action template masks.
> - raw encap added action template mask validation.
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> ---
> Depends-on: series-28881 ("net/mlx5/hws: add support for multi pattern")
> ---
> v2: remove Depends-on: patch
> v3: add Depends-on: series
> ---
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
prev parent reply other threads:[~2023-10-29 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 5:00 [PATCH] " Gregory Etelson
2023-09-19 7:29 ` [PATCH v2] " Gregory Etelson
2023-09-24 9:41 ` [PATCH v3] " Gregory Etelson
2023-10-29 15:51 ` Ori Kam [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=MW2PR12MB46667F415C6DC83C679170E3D6A2A@MW2PR12MB4666.namprd12.prod.outlook.com \
--to=orika@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=suanmingm@nvidia.com \
--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).