From: Raslan Darawsheh <rasland@nvidia.com>
To: Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@nvidia.com>
Subject: RE: [PATCH v2 0/3] net/mlx5: add port representor destination to mirror
Date: Mon, 30 Oct 2023 09:05:54 +0000 [thread overview]
Message-ID: <MN0PR12MB605662283E97F0587A472019CFA1A@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231030022828.973851-1-suanmingm@nvidia.com>
Hi,
> -----Original Message-----
> From: Suanming Mou <suanmingm@nvidia.com>
> Sent: Monday, October 30, 2023 4:28 AM
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Ori Kam
> <orika@nvidia.com>
> Subject: [PATCH v2 0/3] net/mlx5: add port representor destination to mirror
>
> In order to clone the traffic from FDB to NIC TIR, user can set port representor
> action as mirror clone destination. In that case cloned traffic will be moved to
> E-Switch manager root table, and goes to software TIR.
>
> This series adds the port representor support to mirror action.
>
> v2:
> - add Acked-by
> - rebase on top of series [1]
>
> [1]: https://patches.dpdk.org/project/dpdk/list/?series=29662
>
> Suanming Mou (3):
> net/mlx5: add port representor action
> net/mlx5: add port representor destination to mirror
> app/testpmd: add port representor as sample destination
>
> app/test-pmd/cmdline_flow.c | 1 +
> doc/guides/nics/mlx5.rst | 6 +++
> doc/guides/rel_notes/release_23_11.rst | 1 +
> drivers/net/mlx5/mlx5.h | 2 +
> drivers/net/mlx5/mlx5_flow.h | 4 +-
> drivers/net/mlx5/mlx5_flow_hw.c | 74 +++++++++++++++++++++++++-
> 6 files changed, 86 insertions(+), 2 deletions(-)
>
> --
> 2.34.1
Missing this update:
diff --git a/doc/guides/nics/features/mlx5.ini b/doc/guides/nics/features/mlx5.ini
index b5df34d0f1..45bdd20a79 100644
--- a/doc/guides/nics/features/mlx5.ini
+++ b/doc/guides/nics/features/mlx5.ini
@@ -120,6 +120,7 @@ of_push_vlan = Y
of_set_vlan_pcp = Y
of_set_vlan_vid = Y
port_id = Y
+port_representor = Y
quota = I
queue = Y
raw_decap = Y
@@ -143,3 +144,4 @@ set_tp_src = Y
set_ttl = Y
vxlan_decap = Y
vxlan_encap = Y
will add during integration,
series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2023-10-30 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 0:43 [PATCH " Suanming Mou
2023-10-17 0:43 ` [PATCH 1/3] net/mlx5: add port representor action Suanming Mou
2023-10-17 0:44 ` [PATCH 2/3] net/mlx5: add port representor destination to mirror Suanming Mou
2023-10-17 0:44 ` [PATCH 3/3] app/testpmd: add port representor as sample destination Suanming Mou
2023-10-29 13:33 ` [PATCH 0/3] net/mlx5: add port representor destination to mirror Ori Kam
2023-10-30 2:28 ` [PATCH v2 " Suanming Mou
2023-10-30 2:28 ` [PATCH v2 1/3] net/mlx5: add port representor action Suanming Mou
2023-10-30 2:28 ` [PATCH v2 2/3] net/mlx5: add port representor destination to mirror Suanming Mou
2023-10-30 2:28 ` [PATCH v2 3/3] app/testpmd: add port representor as sample destination Suanming Mou
2023-10-30 9:05 ` 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=MN0PR12MB605662283E97F0587A472019CFA1A@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=suanmingm@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).