From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: bingz@nvidia.com, mkashani@nvidia.com, rasland@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 flow engine availability in mlx5 guide
Date: Sat, 29 Nov 2025 13:42:57 +0100 [thread overview]
Message-ID: <20251129124257.1619774-1-thomas@monjalon.net> (raw)
Starting with NVIDIA ConnectX-9, the future devices will support
only hardware steering (HWS) flow engine.
The software steering options (legacy Verbs and Direct Verbs)
have lower performances, and won't be available for new devices.
Fixes: 1b55eeb7b76f ("common/mlx5: add ConnectX-9 SuperNIC")
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/nics/mlx5.rst | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 8481cc974a..904a0ac358 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -689,9 +689,11 @@ for an additional list of options shared with other mlx5 drivers.
- ``dv_flow_en`` parameter [int]
Value 0 means legacy Verbs flow offloading.
+ It is available for devices older than ConnectX-9.
- Value 1 enables the DV flow steering assuming it is supported by the
- driver (requires rdma-core 24 or higher).
+ Value 1 enables the Direct Verbs flow steering.
+ It is available for devices older than ConnectX-9,
+ and requires rdma-core 24 or later.
Value 2 enables the WQE based hardware steering.
In this mode, only queue-based flow management is supported.
@@ -1338,7 +1340,8 @@ Hardware Steering
~~~~~~~~~~~~~~~~~
Faster than software steering (SWS),
-hardware steering (HWS) is the only mode supporting the flow template async API.
+hardware steering (HWS) is the only mode supporting the flow template async API,
+and the only mode supported on device ConnectX-9 and later.
Flow rules are managed by the hardware,
with a WQE-based high scaling and safer flow insertion/destruction.
--
2.51.0
next reply other threads:[~2025-11-29 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 12:42 Thomas Monjalon [this message]
2025-11-29 22:24 ` 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=20251129124257.1619774-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@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).