> -----Original Message-----
> From: Dariusz Sosnowski <dsosnow...@nvidia.com>
> Sent: Sunday, February 26, 2023 4:18 AM
> To: Matan Azrad <ma...@nvidia.com>; Slava Ovsiienko
> <viachesl...@nvidia.com>
> Cc: dev@dpdk.org; sta...@dpdk.org; Ori Kam <or...@nvidia.com>
> Subject: [PATCH 2/2] net/mlx5: fix isolated mode when repr matching is
> disabled
>
> In HW steering mode, when running on an E-Switch setup,
> mlx5 PMD provides an ability to enable or disable representor matching
> (through
> `repr_matching_en` device argument).
> If representor matching is enabled, any ingress or egress flow rule, created
> on
> any port representor will match traffic related to that specific port.
> If it is disabled, flow rule created on one of the ports, will match traffic
> related
> to all ports.
>
> As a result, when representor matching is disabled, PMD cannot correctly
> create
> control flow rules for receiving default traffic according to port
> configuration.
> Since each port representor in the same switch domain, can have different port
> configuration and flow rules do not differentiate between ports, these flow
> rules cannot be correctly applied.
> In that case, each port works in de facto isolated mode.
>
> This patch makes sure that if representor matching is disabled, port is forced
> into isolated mode. Disabling flow isolated is forbidden.
>
> Fixes: 483181f7b6dd ("net/mlx5: support device control of representor
> matching")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnow...@nvidia.com>
> Acked-by: Ori Kam <or...@nvidia.com>
Acked-by: Suanming Mou <suanmi...@nvidia.com>
Thanks.
