[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZD1K8NtWTmKkhfUN@corigine.com>
Date: Mon, 17 Apr 2023 15:34:40 +0200
From: Simon Horman <simon.horman@...igine.com>
To: Leon Romanovsky <leon@...nel.org>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Leon Romanovsky <leonro@...dia.com>,
Steffen Klassert <steffen.klassert@...unet.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
netdev@...r.kernel.org, Saeed Mahameed <saeedm@...dia.com>,
Raed Salem <raeds@...dia.com>, Emeel Hakim <ehakim@...dia.com>
Subject: Re: [PATCH net-next v1 08/10] net/mlx5: Allow blocking encap changes
in eswitch
On Thu, Apr 13, 2023 at 03:29:26PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.com>
>
> Existing eswitch encap option enables header encapsulation. Unfortunately
> currently available hardware isn't able to perform double encapsulation,
> which can happen once IPsec packet offload tunnel mode is used together
> with encap mode set to BASIC.
>
> So as a solution for misconfiguration, provide an option to block encap
> changes, which will be used for IPsec packet offload.
>
> Reviewed-by: Emeel Hakim <ehakim@...dia.com>
> Signed-off-by: Leon Romanovsky <leonro@...dia.com>
Reviewed-by: Simon Horman <simon.horman@...igine.com>
Powered by blists - more mailing lists