Add limitation for unified FDB group 0 table creation.
Signed-off-by: Maayan Kashani <mkash...@nvidia.com>
Acked-by: Bing Zhao <bi...@nvidia.com>
---
doc/guides/nics/mlx5.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 190c58b54d6..efa4c708d51 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -288,6 +288,12 @@ Limitations
- RTE_FLOW_ITEM_TYPE_MPLS matching is not supported on group 0.
- mpls_encap and mpls_decap actions support only one level of MPLS.
+ - Template table with flags wire_orig/vport_orig cannot be created
+ on group 0 (group 1 in practice), since group 0 is created on startup
+ in UNIFIED_FDB domain.
+
+ - rte_flow_action_mark id is not supported in FDB_TX domain.
+
- When using Verbs flow engine (``dv_flow_en`` = 0), flow pattern without any
specific VLAN will match for VLAN packets as well:
--
2.21.0
