[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZBgjsw8exj1c46lW@gauss3.secunet.de>
Date: Mon, 20 Mar 2023 10:13:23 +0100
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Leon Romanovsky <leon@...nel.org>
CC: Raed Salem <raeds@...dia.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Jakub Kicinski <kuba@...nel.org>, <netdev@...r.kernel.org>,
Paolo Abeni <pabeni@...hat.com>,
Paul Blakey <paulb@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [PATCH xfrm-next 4/9] xfrm: add new device offload acquire flag
On Tue, Mar 14, 2023 at 10:58:39AM +0200, Leon Romanovsky wrote:
> From: Raed Salem <raeds@...dia.com>
>
> During XFRM acquire flow, a default SA is created to be updated later,
> once acquire netlink message is handled in user space. When the relevant
> policy is offloaded this default SA is also offloaded to IPsec offload
> supporting driver, however this SA does not have context suitable for
> offloading in HW, nor is interesting to offload to HW, consequently needs
> a special driver handling apart from other offloaded SA(s).
> Add a special flag that marks such SA so driver can handle it correctly.
>
> Signed-off-by: Raed Salem <raeds@...dia.com>
> Signed-off-by: Leon Romanovsky <leonro@...dia.com>
Acked-by: Steffen Klassert <steffen.klassert@...unet.com>
Powered by blists - more mailing lists