From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
To: dsosnowski@nvidia.com
Cc: dev@dpdk.org, rasland@nvidia.com, stable@dpdk.org,
viacheslavo@nvidia.com, bingz@nvidia.com, orika@nvidia.com,
suanmingm@nvidia.com, matan@nvidia.com
Subject: Re: [PATCH] doc/mlx5: document firmware requirement for flex item
Date: Wed, 16 Jul 2025 03:49:40 -0400 [thread overview]
Message-ID: <20250716075013.3539970-1-14pwcse1224@uetpeshawar.edu.pk> (raw)
In-Reply-To: <20250715125249.hwrzd4aasfjhhyxa@ds-vm-debian.local>
Hi Dariusz,
Thanks for the follow-up.
I was using DPDK v23.11 with the following flex item configuration:
{
"next_header": { "field_mode": "FIELD_MODE_FIXED", "field_size": 0, "field_base": 0 },
"next_protocol": { "field_mode": "FIELD_MODE_FIXED", "field_size": 8, "field_base": 72 },
"sample_data": [
{ "field_mode": "FIELD_MODE_FIXED", "field_size": 32, "field_base": 0 },
{ "field_mode": "FIELD_MODE_FIXED", "field_size": 32, "field_base": 32 },
{ "field_mode": "FIELD_MODE_FIXED", "field_size": 32, "field_base": 64 },
{ "field_mode": "FIELD_MODE_FIXED", "field_size": 32, "field_base": 96 }
],
"input_link": [
{ "item": "eth type is 0x08802" }
],
"output_link": [
{ "item": "udp", "next": 17 },
{ "item": "tcp", "next": 6 }
]
}
With firmware version 24.30.1004 (MT_0000000704), the following error was produced:
port-0: flex item #3 creation failed: unsupported header length field mode (FIXED)
After upgrading to firmware version 24.38.1002, the same configuration succeeded.
Example flow after upgrade:
testpmd> flow flex_item pattern 2 spec 45000000000000000000000001020304 mask FF0000000000000000000000FFFFFFFF
created pattern #2
testpmd> flow create 0 ingress pattern eth / ipv4 / udp / flex item is 3 pattern is 2 / end actions mark id 1 / queue index 0 / end
Flow rule #0 created
It appears this issue was resolved at the firmware level.
Best regards,
Khadem Ullah
prev parent reply other threads:[~2025-07-16 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 11:49 Khadem Ullah
2025-07-15 12:52 ` Dariusz Sosnowski
2025-07-16 7:49 ` Khadem Ullah [this message]
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=20250716075013.3539970-1-14pwcse1224@uetpeshawar.edu.pk \
--to=14pwcse1224@uetpeshawar.edu.pk \
--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=stable@dpdk.org \
--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).