Currently a matcher can only be created and attached to a NIC RX flow table. Extend it to allow it on NIC TX flow tables as well. In order to achieve that, we: 1) Expose a new attribute: MLX5_IB_ATTR_FLOW_MATCHER_FLOW_FLAGS. enum ib_flow_flags is used as valid flags. Only IB_FLOW_ATTR_FLAGS_EGRESS is supported. 2) Remove the requirement to have a DEVX or QP destination when creating a flow. A flow added to NIC TX flow table will forward the packet outside of the vport (Wire or E-Switch in the SR-iOV case).
Showing the changes to include/uapi (1 of 3 files). Show all
Unified · Split
| @@ -125,6 +125,7 @@ enum mlx5_ib_flow_matcher_create_attrs { · 124 unmodified lines | |||
| 125 | MLX5_IB_ATTR_FLOW_MATCHER_MATCH_MASK, | 125 | MLX5_IB_ATTR_FLOW_MATCHER_MATCH_MASK, |
| 126 | MLX5_IB_ATTR_FLOW_MATCHER_FLOW_TYPE, | 126 | MLX5_IB_ATTR_FLOW_MATCHER_FLOW_TYPE, |
| 127 | MLX5_IB_ATTR_FLOW_MATCHER_MATCH_CRITERIA, | 127 | MLX5_IB_ATTR_FLOW_MATCHER_MATCH_CRITERIA, |
| 128 | MLX5_IB_ATTR_FLOW_MATCHER_FLOW_FLAGS, | ||
| 128 | }; | 129 | }; |
| 129 | 130 | ||
| 130 | enum mlx5_ib_flow_matcher_destroy_attrs { | 131 | enum mlx5_ib_flow_matcher_destroy_attrs { |