From: Alexander Kozyrev <akozyrev@nvidia.com>
To: <dev@dpdk.org>
Cc: <rasland@nvidia.com>, <viacheslavo@nvidia.com>,
<dsosnowski@nvidia.com>, <bingz@nvidia.com>,
<suanmingm@nvidia.com>
Subject: [PATCH] doc: document hash RSS limitations with CQE zipping
Date: Fri, 10 Jan 2025 00:34:27 +0200 [thread overview]
Message-ID: <20250109223432.3222546-1-akozyrev@nvidia.com> (raw)
RSS hash is only fully supported when the Hash RSS format is selected.
Update MLX5 documentation about lack of RTE_MBUF_F_RX_RSS_HASH flag for
some packets in case of any other CQE compression format is configured.
Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
---
doc/guides/nics/mlx5.rst | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 30c40f767b..ceea2dd320 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -497,9 +497,12 @@ Limitations
cannot be used in conjunction with MPRQ
since packets may be already attached to PMD-managed external buffers.
-- If Multi-Packet Rx queue is configured (``mprq_en``) and Rx CQE compression is
+- RSS hash result is only fully supported when the Hash RSS format is selected
+ as the current CQE compression format on the RX side (``rxq_cqe_comp_en``).
+ Any other format leads to no RTE_MBUF_F_RX_RSS_HASH flag for some Rx packets.
+ If a Multi-Packet Rx queue is configured (``mprq_en``) and Rx CQE compression is
enabled (``rxq_cqe_comp_en``) at the same time, RSS hash result is not fully
- supported. Some Rx packets may not have RTE_MBUF_F_RX_RSS_HASH.
+ supported, as the Checksum format is selected by default in this case.
- IPv6 Multicast messages are not supported on VM, while promiscuous mode
and allmulticast mode are both set to off.
--
2.43.5
next reply other threads:[~2025-01-09 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 22:34 Alexander Kozyrev [this message]
2025-01-10 8:55 ` Dariusz Sosnowski
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=20250109223432.3222546-1-akozyrev@nvidia.com \
--to=akozyrev@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@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).