DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shun Hao <shunh@nvidia.com>
To: <viacheslavo@nvidia.com>, <matan@nvidia.com>, <orika@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH v1 0/3] Add HWS mirroring support
Date: Thu, 28 Sep 2023 16:09:10 +0300	[thread overview]
Message-ID: <20230928130913.2583907-1-shunh@nvidia.com> (raw)

This patch series are to add the support of mirroring feature in HWS.
The main idea is to create DevX Flow table and FTE in it. The FTE may
have multiple different destinations of type Vport/TIR/Table. With this
multi-destination FTE, NIC can duplicate packets and forward to all
destinations.

Hamdan Igbaria (2):
  net/mlx5/hws: add creation of packet reformat DevX obj
  net/mlx5/hws: add mlx5dr obj struct to mlx5dr action

Shun Hao (1):
  net/mlx5/hws: add support for mirroring

 drivers/common/mlx5/mlx5_prm.h         |  62 +++++++++++-
 drivers/net/mlx5/hws/mlx5dr.h          |  34 +++++++
 drivers/net/mlx5/hws/mlx5dr_action.c   | 134 ++++++++++++++++++++++++-
 drivers/net/mlx5/hws/mlx5dr_action.h   |   6 ++
 drivers/net/mlx5/hws/mlx5dr_cmd.c      | 123 +++++++++++++++++++++--
 drivers/net/mlx5/hws/mlx5dr_cmd.h      |  30 +++++-
 drivers/net/mlx5/hws/mlx5dr_debug.c    |   1 +
 drivers/net/mlx5/hws/mlx5dr_internal.h |   5 +
 drivers/net/mlx5/hws/mlx5dr_send.c     |   5 -
 drivers/net/mlx5/hws/mlx5dr_table.c    |   8 +-
 10 files changed, 384 insertions(+), 24 deletions(-)

-- 
2.20.0


             reply	other threads:[~2023-09-28 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 13:09 Shun Hao [this message]
2023-09-28 13:09 ` [PATCH v1 1/3] net/mlx5/hws: add creation of packet reformat DevX obj Shun Hao
2023-09-28 13:09 ` [PATCH v1 2/3] net/mlx5/hws: add mlx5dr obj struct to mlx5dr action Shun Hao
2023-09-28 13:09 ` [PATCH v1 3/3] net/mlx5/hws: add support for mirroring Shun Hao

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=20230928130913.2583907-1-shunh@nvidia.com \
    --to=shunh@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@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).