[PATCH] net/mlx5: fix default flow engine on Windows

Raslan Darawsheh rasland at nvidia.com
Tue Mar 10 10:44:35 CET 2026


Hi,


On 09/03/2026 2:47 PM, Dariusz Sosnowski wrote:
> Offending patch has changed the logic for handling default
> configuration for dv_flow_en device argument.
> This change has introduced a regression to Windows support.
> On Windows, mlx5 PMD only supports flow API implementation
> with dv_flow_en set to 1. With the change, this argument value was
> changed based on device capabilities.
> On newer NICs, dv_flow_en would be set to HW Steering flow engine
> which is not supported on Windows.
> On older NICs, it would be set to Verbs engine, which is also not
> supported.
> 
> This patch fixes that by introducing platform-specific initialization
> and fixup of relevant device arguments i.e., dv_flow_en and
> allow_duplicate_pattern.
> On Linux the existing logic is kept. On Windows dv_flow_en and
> allow_duplicate_pattern are set by default to 1 (same as before
> the offending patch).
> 
> Fixes: 170ebe941be3 ("net/mlx5: fix flow devargs handling for future HW")
> 
> Signed-off-by: Maayan Kashani <mkashani at nvidia.com>
> Signed-off-by: Dariusz Sosnowski <dsosnowski at nvidia.com>
> Acked-by: Bing Zhao <bingz at nvidia.com>
Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh



More information about the dev mailing list