DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jiawei Wang <jiaweiw@nvidia.com>
To: <suanmingm@nvidia.com>, <viacheslavo@nvidia.com>,
	<thomas@monjalon.net>, Matan Azrad <matan@nvidia.com>,
	Ori Kam <orika@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH] doc: clarify mirroring limitations in mlx5 guide
Date: Tue, 7 Nov 2023 17:10:07 +0200	[thread overview]
Message-ID: <20231107151007.31044-1-jiaweiw@nvidia.com> (raw)

Update the description of flow mirroring to make clear
what are the limitations of the mlx5 driver.

Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
---
 doc/guides/nics/mlx5.rst | 22 +++++++++++++---------
 1 file changed, 13 insertions(+), 9 deletions(-)

diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 45379960f0..b2ac7c5097 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -537,19 +537,23 @@ Limitations
 
   - Supports ``RTE_FLOW_ACTION_TYPE_SAMPLE`` action only within NIC Rx and
     E-Switch steering domain.
-  - For E-Switch Sampling flow with sample ratio > 1, additional actions are not
-    supported in the sample actions list.
+  - In E-Switch steering domain, for sampling with sample ratio > 1 in a transfer rule,
+    additional actions are not supported in the sample actions list.
   - For ConnectX-5, the ``RTE_FLOW_ACTION_TYPE_SAMPLE`` is typically used as
     first action in the E-Switch egress flow if with header modify or
     encapsulation actions.
-  - For NIC Rx flow, supports ``MARK``, ``COUNT``, ``QUEUE``, ``RSS`` in the
+  - For NIC Rx flow, supports only ``MARK``, ``COUNT``, ``QUEUE``, ``RSS`` in the
     sample actions list.
-  - For E-Switch mirroring flow, supports ``RAW_ENCAP``, ``PORT_ID``,
-    ``VXLAN_ENCAP``, ``NVGRE_ENCAP`` in the sample actions list.
-  - For E-Switch mirroring flow with sample ratio = 1, the ``ENCAP`` action
-    supports uplink port only.
-  - For E-Switch mirroring flow with sample ratio = 1, the ``PORT`` and ``JUMP`` actions
-    are not supported without presented ``ENCAP`` action in the sample actions list.
+  - In E-Switch steering domain, for mirroring with sample ratio = 1 in a transfer rule,
+    supports only ``RAW_ENCAP``, ``PORT_ID``, ``REPRESENTED_PORT``, ``VXLAN_ENCAP``, ``NVGRE_ENCAP``
+    in the sample actions list.
+  - In E-Switch steering domain, for mirroring with sample ratio = 1 in a transfer rule,
+    the encapsulation actions (``RAW_ENCAP`` or ``VXLAN_ENCAP`` or ``NVGRE_ENCAP``)
+    support for uplink port only.
+  - In E-Switch steering domain, for mirroring with sample ratio = 1 in a transfer rule,
+    the port actions (``PORT_ID`` or ``REPRESENTED_PORT``) with uplink port and ``JUMP`` action
+    are not supported without the encapsulation actions (``RAW_ENCAP`` or ``VXLAN_ENCAP`` or ``NVGRE_ENCAP``)
+    in the sample actions list.
   - For ConnectX-5 trusted device, the application metadata with SET_TAG index 0
     is not supported before ``RTE_FLOW_ACTION_TYPE_SAMPLE`` action.
 
-- 
2.18.1


             reply	other threads:[~2023-11-07 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 15:10 Jiawei Wang [this message]
2023-11-27 11:08 ` Thomas Monjalon

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=20231107151007.31044-1-jiaweiw@nvidia.com \
    --to=jiaweiw@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --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).