* [PATCH] doc: document group 0 IPv6 fragment VLAN limitation
@ 2026-11-01 16:04 Maayan Kashani
2026-11-05 7:37 ` Raslan Darawsheh
0 siblings, 1 reply; 2+ messages in thread
From: Maayan Kashani @ 2026-11-01 16:04 UTC (permalink / raw)
To: dev
Cc: rasland, dsosnowski, viacheslavo, bingz, orika, suanmingm, matan,
Maayan Kashani
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-05 7:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-01 16:04 [PATCH] doc: document group 0 IPv6 fragment VLAN limitation Maayan Kashani
2026-11-05 7:37 ` Raslan Darawsheh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox