[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZS5WK8V0+JoTlNmu@gauss3.secunet.de>
Date: Tue, 17 Oct 2023 11:38:51 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Leon Romanovsky <leon@...nel.org>
CC: Patrisious Haddad <phaddad@...dia.com>, Herbert Xu
<herbert@...dor.apana.org.au>, <netdev@...r.kernel.org>, Raed Salem
<raeds@...dia.com>, Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [PATCH xfrm-next 5/9] net/mlx5e: Unify esw and normal IPsec
status table creation/destruction
On Mon, Oct 16, 2023 at 12:15:13PM +0300, Leon Romanovsky wrote:
> From: Patrisious Haddad <phaddad@...dia.com>
>
> Change normal IPsec flow to use the same creation/destruction functions
> for status flow table as that of ESW, which first of all refines the
> code to have less code duplication.
>
> And more importantly, the ESW status table handles IPsec syndrome
> checks at steering by HW, which is more efficient than the previous
> behaviour we had where it was copied to WQE meta data and checked
> by the driver.
>
> Signed-off-by: Patrisious Haddad <phaddad@...dia.com>
> Signed-off-by: Leon Romanovsky <leonro@...dia.com>
This one does not apply to the ipsec-next tree.
Powered by blists - more mailing lists