[PATCH 1/3] net/mlx5: fix multi process Tx default rules
Raslan Darawsheh
rasland at nvidia.com
Sun Nov 2 08:32:24 CET 2025
Hi,
On 29/10/2025 5:57 PM, Gregory Etelson wrote:
> From: Michael Baum <michaelba at nvidia.com>
>
> When representor matching is disabled, an egress default rule is
> inserted which matches all and copies REG_A to REG_C_1 (when dv_xmeta_en
> == 4) and jump to group 1. All user rules started from group 1.
>
> When 2 processes are working together, the first one creates this flow
> rule and the second one is failed with errno EEXIST. This renders all
> user egress rules in 2nd process to be invalid.
>
> This patch changes this default rule match on SQs.
>
> Fixes: 483181f7b6dd ("net/mlx5: support device control of representor matching")
> Cc: dsosnowski at nvidia.com
>
> Signed-off-by: Michael Baum <michaelba at nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski at nvidia.com>
>
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
More information about the dev
mailing list