From: Raslan Darawsheh <rasland@nvidia.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: [PATCH] doc/mlx4: set limitation for RSS
Date: Sun, 19 Nov 2023 15:24:30 +0200 [thread overview]
Message-ID: <20231119132430.3666-1-rasland@nvidia.com> (raw)
This adds a limitation explanation on RSS queue usage
for MLX4 pmd.
MLX4 pmd requires a power of two queues to do RSS
but, the user can still open more queues which can be utilized
through flow API.
Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
---
doc/guides/nics/mlx4.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index c6279f51d0..f59e52a671 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -145,6 +145,18 @@ Limitations
- TSO (Transmit Segmentation Offload) is supported in OFED version
4.4 and above.
+- RSS only works on power of two number of queues.
+- The user can open none power of two queues, but the PMD will round down
+ to the highest power of two queues by default for RSS.
+ Other queues can be utilized through flow API.
+ example::
+ ./dpdk-testpmd -a 08:00.0 -- -i --rxq 12 --txq 12 --rss-ip
+
+ The first 8 queues will be used by default for RSS over IP.
+ The rest of the queues can be utilized through rte flow like the following::
+ flow create 0 ingress pattern eth / ipv4 / tcp / end actions rss queues 8 9 10 11 end / end
+
+
Prerequisites
-------------
--
2.25.1
next reply other threads:[~2023-11-19 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 13:24 Raslan Darawsheh [this message]
2023-11-27 11:27 ` 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=20231119132430.3666-1-rasland@nvidia.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).