From: Maayan Kashani <mkashani@nvidia.com>
To: <dev@dpdk.org>
Cc: <mkashani@nvidia.com>, <rasland@nvidia.com>,
Bing Zhao <bingz@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: [PATCH] doc: update IPv6 5-tuple matching limitation
Date: Thu, 7 Aug 2025 12:17:45 +0300 [thread overview]
Message-ID: <20250807091746.155668-1-mkashani@nvidia.com> (raw)
Update IPv6 5-tuple matching limitation,
in newer HW, IPv6 5-tuple matching is
supported.
Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
Acked-by: Bing Zhao <bingz@nvidia.com>
---
doc/guides/nics/mlx5.rst | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 86fe747c166..97a200443ec 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -1381,8 +1381,6 @@ Limitations
- ``-EAGAIN`` for ``rte_eth_dev_start()``.
- ``-EBUSY`` for ``rte_eth_dev_stop()``.
-#. Partial match with item template is not supported.
-
#. The supported actions order is as below::
MARK (a)
@@ -3324,7 +3322,13 @@ See :ref:`mlx5_firmware_config` for more details about the flex parser profile.
Limitations
^^^^^^^^^^^
-#. IPv6 5-tuple matching is not supported with :ref:`HW steering <mlx5_hws>`.
+#. IPv6 5-tuple matching is supported with :ref:`HW steering <mlx5_hws>`
+ from ConnectX-8/BlueField-3.
+ Previous NICs support matching on either IPv6 src or dst in a rule.
+ In general, the matching limitation is related to the number of DWORDS:
+ older hardware supports up to 5 DWORDS for matching,
+ while newer hardware (ConnectX-8/BlueField-3 and up)
+ supports up to 11 DWORDS for matching.
#. IPv6 multicast messages are not supported on VM,
while promiscuous mode and allmulticast mode are both set to off.
--
2.21.0
reply other threads:[~2025-08-07 9:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250807091746.155668-1-mkashani@nvidia.com \
--to=mkashani@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@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).