[v7,12/12] doc: add E-Switch sample flow limitation description
Checks
Commit Message
Add description about the E-Switch sample flow limitation.
Due to Metadata register c0 is deleted while doing the loopback,
so that only support forward the sampling packet into
e-switch manager port, no additional action support in sample flow.
Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
doc/guides/nics/mlx5.rst | 5 +++++
1 file changed, 5 insertions(+)
@@ -311,6 +311,11 @@ Limitations
for some NICs (such as ConnectX-6 Dx and BlueField 2).
The capability bit ``scatter_fcs_w_decap_disable`` shows NIC support.
+- E-Switch Sample flow:
+
+ - The E-Switch Sample flow must have the eswitch_manager VPORT destination (PF or ECPF) and no additional actions.
+ - For ConnectX-5, the ``RTE_FLOW_ACTION_TYPE_SAMPLE`` is typically used as first action in the E-Switch egress flow if with header modify or encapsulation actions.
+
Statistics
----------