From: Maayan Kashani <mkashani@nvidia.com>
To: <dev@dpdk.org>
Cc: <rasland@nvidia.com>, <dsosnowski@nvidia.com>,
<viacheslavo@nvidia.com>, <bingz@nvidia.com>, <orika@nvidia.com>,
<suanmingm@nvidia.com>, <matan@nvidia.com>,
Maayan Kashani <mkashani@nvidia.com>
Subject: [PATCH] doc: document group 0 IPv6 fragment VLAN limitation
Date: Sun, 1 Nov 2026 18:04:43 +0200 [thread overview]
Message-ID: <20261101160443.3216180-1-mkashani@nvidia.com> (raw)
Matching a VLAN item together with an exact IPv6 fragment next_hdr
misses on the hardware root table, while the same pattern matches
in a non-root group. Document the limitation and the supported
group 0 alternatives.
Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
doc/guides/nics/mlx5.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index c7bb6eb182e..8dd7ee9a969 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -3731,6 +3731,14 @@ Limitations
and the first IP fragment is received,
then this IP fragment will miss on that flow rule.
+#. Matching ``RTE_FLOW_ITEM_TYPE_VLAN`` together with an exact
+ ``next_hdr`` of ``RTE_FLOW_ITEM_TYPE_IPV6_FRAG_EXT``
+ is not supported on group 0 (HW root table).
+ The rule is accepted, but matching packets do not hit it.
+ Create this pattern in a non-root group.
+ On group 0, a VLAN item with a wildcard fragment ``next_hdr``,
+ and an exact ``next_hdr`` without a VLAN item, are supported.
+
.. _mlx5_nat64:
--
2.25.1
reply other threads:[~2026-11-01 16:05 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=20261101160443.3216180-1-mkashani@nvidia.com \
--to=mkashani@nvidia.com \
--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=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