DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Maayan Kashani <mkashani@nvidia.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: Re: [PATCH 0/2] validate actions in HWS table
Date: Tue, 4 Jun 2024 11:49:06 +0000	[thread overview]
Message-ID: <MN0PR12MB6056D71312FAB074F2336B9DCFF82@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240602060051.42910-1-getelson@nvidia.com>

Hi,

From: Gregory Etelson <getelson@nvidia.com>
Sent: Sunday, June 2, 2024 9:00 AM
To: dev@dpdk.org
Cc: Gregory Etelson; Maayan Kashani; Raslan Darawsheh; Dariusz Sosnowski
Subject: [PATCH 0/2] validate actions in HWS table

Validate flow actions before creation of HWS template table.

Gregory Etelson (2):
  net/mlx5: fix access to PMD template API
  net/mlx5: validate flow actions in table creation

 drivers/net/mlx5/mlx5.h            |  13 +
 drivers/net/mlx5/mlx5_flow.c       |  15 +-
 drivers/net/mlx5/mlx5_flow.h       |  33 ++-
 drivers/net/mlx5/mlx5_flow_dv.c    |  20 +-
 drivers/net/mlx5/mlx5_flow_hw.c    | 453 +++++++++++++++++++++++++----
 drivers/net/mlx5/mlx5_flow_verbs.c |   2 +-
 6 files changed, 467 insertions(+), 69 deletions(-)

Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh


      parent reply	other threads:[~2024-06-04 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02  6:00 Gregory Etelson
2024-06-02  6:00 ` [PATCH 1/2] net/mlx5: fix access to PMD template API Gregory Etelson
2024-06-02  6:00 ` [PATCH 2/2] net/mlx5: validate flow actions in table creation Gregory Etelson
2024-06-04 11:49 ` 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=MN0PR12MB6056D71312FAB074F2336B9DCFF82@MN0PR12MB6056.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=mkashani@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).