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 <[email protected]> Acked-by: Dariusz Sosnowski <[email protected]> --- 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
