Hello David,

> Tunnel offloading is linked to running a port with the non-obvious
> dv_xmeta_en=3 devargs. Hint at it for "normal" users.
> 
> Fixes: 4ec6360de37d ("net/mlx5: implement tunnel offload")
> 
> Signed-off-by: David Marchand <david.march...@redhat.com>
> ---
>  drivers/net/mlx5/mlx5_flow.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
> index d0275fdd00..51f6ecd25d 100644
> --- a/drivers/net/mlx5/mlx5_flow.c
> +++ b/drivers/net/mlx5/mlx5_flow.c
> @@ -11295,7 +11295,7 @@ mlx5_flow_tunnel_validate(struct rte_eth_dev
> *dev,
>         if (!is_tunnel_offload_active(dev))
>                 return rte_flow_error_set(error, ENOTSUP,
>                                           RTE_FLOW_ERROR_TYPE_ACTION_CONF, 
> NULL,
> -                                         "tunnel offload was not activated");
> +                                         "tunnel offload was not activated, 
> consider
> setting dv_xmeta_en=3");
>         if (!tunnel)
>                 return rte_flow_error_set(error, EINVAL,
>                                           RTE_FLOW_ERROR_TYPE_ACTION_CONF, 
> NULL,
> --
> 2.40.0

Reviewed-by: Gregory Etelson <getel...@nvidia.com>

Reply via email to