From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
To: dev@dpdk.org
Cc: rasland@nvidia.com, stable@dpdk.org,
Khadem Ullah <khadem@dreambigsemi.com>,
Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Subject: [PATCH] doc/mlx5: document firmware requirement for flex item
Date: Tue, 8 Jul 2025 07:49:21 -0400 [thread overview]
Message-ID: <20250708114921.1031027-1-khadem@dreambigsemi.com> (raw)
Some BlueField firmware versions (e.g. 24.30.1004) do not support flex item
definitions using FIELD_MODE_FIXED with size set to 0, such as in 'next_header'.
Attempting to use this configuration may result in the following error:
'unsupported header length field mode (FIXED)'
This is resolved starting from firmware version 24.38.1002.
The patch adds a note to the mlx5 guide explaining the firmware requirement
for such flex item configurations.
Fixes: 16508bfd0816 ('net/mlx5: doc: add flex item specifications in mlx5 guide')
Cc: stable@dpdk.org
Signed-off-by: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
---
doc/guides/nics/mlx5.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index c3a350d24e..1b0e3efc41 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -476,6 +476,10 @@ Limitations
- In flex item configuration, ``next_header.field_base`` value
must be byte aligned (multiple of 8).
- Modify field with flex item, the offset must be byte aligned (multiple of 8).
+ .. note::
+ Some firmware versions (e.g. 24.30.1004) do not support
+ ``next_header`` with ``field_mode = FIELD_MODE_FIXED`` and zero size.
+ A newer firmware (e.g. >= 24.38.1002) is required to support this configuration.
- Match on random value:
--
2.43.0
reply other threads:[~2025-07-08 11:49 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=20250708114921.1031027-1-khadem@dreambigsemi.com \
--to=14pwcse1224@uetpeshawar.edu.pk \
--cc=dev@dpdk.org \
--cc=khadem@dreambigsemi.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
/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).