DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gregory Etelson <getelson@nvidia.com>
To: <dev@dpdk.org>
Cc: <getelson@nvidia.com>, <mkashani@nvidia.com>,
	<rasland@nvidia.com>, "Alex Vesker" <valex@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: [PATCH 00/10] net/mlx5/hws: IPSEC reparse submission
Date: Tue, 31 Oct 2023 14:25:02 +0200	[thread overview]
Message-ID: <20231031122512.434686-1-getelson@nvidia.com> (raw)

IPSEC reparse submission.

Alex Vesker (3):
  net/mlx5/hws: allow jump to TIR over FDB
  net/mlx5/hws: support dynamic re-parse
  net/mlx5/hws: dynamic re-parse for modify header

Hamdan Igbaria (6):
  net/mlx5/hws: support IPsec encryption/decryption action
  net/mlx5/hws: support ASO IPsec action
  net/mlx5/hws: support reformat trailer action
  net/mlx5/hws: support ASO first hit action
  net/mlx5/hws: support insert header action
  net/mlx5/hws: support remove header action

Itamar Gozlan (1):
  net/mlx5/hws: check the rule status on rule update

 drivers/common/mlx5/mlx5_prm.h         |  41 +-
 drivers/net/mlx5/hws/mlx5dr.h          | 198 ++++++++
 drivers/net/mlx5/hws/mlx5dr_action.c   | 615 +++++++++++++++++++++++--
 drivers/net/mlx5/hws/mlx5dr_action.h   |  64 ++-
 drivers/net/mlx5/hws/mlx5dr_cmd.c      |  27 +-
 drivers/net/mlx5/hws/mlx5dr_cmd.h      |  10 +-
 drivers/net/mlx5/hws/mlx5dr_context.c  |  15 +
 drivers/net/mlx5/hws/mlx5dr_context.h  |   9 +-
 drivers/net/mlx5/hws/mlx5dr_debug.c    |   7 +
 drivers/net/mlx5/hws/mlx5dr_internal.h |   1 +
 drivers/net/mlx5/hws/mlx5dr_matcher.c  |   7 +
 drivers/net/mlx5/hws/mlx5dr_pat_arg.c  |  41 +-
 drivers/net/mlx5/hws/mlx5dr_pat_arg.h  |   2 +
 drivers/net/mlx5/hws/mlx5dr_rule.c     |   6 +
 14 files changed, 973 insertions(+), 70 deletions(-)

Reviewed-by: Alex Vesker <valex@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

-- 
2.39.2


             reply	other threads:[~2023-10-31 12:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 12:25 Gregory Etelson [this message]
2023-10-31 12:25 ` [PATCH 01/10] net/mlx5/hws: check the rule status on rule update Gregory Etelson
2023-10-31 12:25 ` [PATCH 02/10] net/mlx5/hws: support IPsec encryption/decryption action Gregory Etelson
2023-10-31 12:25 ` [PATCH 03/10] net/mlx5/hws: support ASO IPsec action Gregory Etelson
2023-10-31 12:25 ` [PATCH 04/10] net/mlx5/hws: support reformat trailer action Gregory Etelson
2023-10-31 12:25 ` [PATCH 05/10] net/mlx5/hws: support ASO first hit action Gregory Etelson
2023-10-31 12:25 ` [PATCH 06/10] net/mlx5/hws: support insert header action Gregory Etelson
2023-10-31 12:25 ` [PATCH 07/10] net/mlx5/hws: support remove " Gregory Etelson
2023-10-31 12:25 ` [PATCH 08/10] net/mlx5/hws: allow jump to TIR over FDB Gregory Etelson
2023-10-31 12:25 ` [PATCH 09/10] net/mlx5/hws: support dynamic re-parse Gregory Etelson
2023-10-31 12:25 ` [PATCH 10/10] net/mlx5/hws: dynamic re-parse for modify header Gregory Etelson

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=20231031122512.434686-1-getelson@nvidia.com \
    --to=getelson@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=valex@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).