doc: update limitations for match with compare result item

In switch mode with enabled `repr_matching_en` devarg flag, the match with compare result item is not supported for `ingress` rules. This is due to an implicit REPRESENTED_PORT being added to the matcher, which conflicts with the single item limitation for match with compare result item. Update the documentation to reflect this limitation in the MLX5 driver guide. Fixes: cb25df7 ("net/mlx5: support comparison matching") Cc: [email protected] Signed-off-by: Suanming Mou <[email protected]> Acked-by: Bing Zhao <[email protected]>
DPDK · Nov 26, 2024 · 340a571 · 340a571
1 parent 03260e1
commit 340a571
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
@@ -468,6 +468,11 @@ Limitations
   - The field type ``RTE_FLOW_FIELD_VALUE`` must be the base (``b``) field.
   - The field type ``RTE_FLOW_FIELD_RANDOM`` can only be compared with
     ``RTE_FLOW_FIELD_VALUE``.
+  - In switch mode, when the ``repr_matching_en`` flag is enabled in the devarg
+    (which is the default setting), the match with compare result item is not
+    supported for ``ingress`` rules. This is because an implicit REPRESENTED_PORT
+    needs to be added to the matcher, which conflicts with the single item
+    limitation for the match with compare result item.
 
 - No Tx metadata go to the E-Switch steering domain for the Flow group 0.
   The flows within group 0 and set metadata action are rejected by hardware.