* [PATCH] doc: add root table encap and decap limitation in mlx5 guide
@ 2026-11-09 13:35 Maayan Kashani
2026-11-11 13:11 ` Raslan Darawsheh
0 siblings, 1 reply; 2+ messages in thread
From: Maayan Kashani @ 2026-11-09 13:35 UTC (permalink / raw)
To: dev
Cc: rasland, dsosnowski, viacheslavo, bingz, orika, suanmingm, matan,
Maayan Kashani
With HW steering, tunnel encapsulation on the root table is supported
only on egress, and tunnel decapsulation only on ingress. This matches
the root packet-reformat validation in the kernel.
Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
doc/guides/nics/mlx5.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 86fe747c166..45efa76bcfe 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -3048,6 +3048,11 @@ Limitations
#. The decapsulation is always done up to the outermost tunnel detected by the HW.
+#. With :ref:`HW steering <mlx5_hws>`, on the HW root table:
+
+ - Encapsulating traffic into an L2 or L3 tunnel is supported only on egress.
+ - Decapsulating an L2 or L3 tunnel is supported only on ingress.
+
.. _mlx5_modify:
--
2.25.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-11 13:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-09 13:35 [PATCH] doc: add root table encap and decap limitation in mlx5 guide Maayan Kashani
2026-11-11 13:11 ` Raslan Darawsheh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox