[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yyg23x8HtBqiB1Oc@unreal>
Date: Mon, 19 Sep 2022 12:31:11 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Steffen Klassert <steffen.klassert@...unet.com>
Cc: "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>, Raed Salem <raeds@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>,
Bharat Bhushan <bbhushan2@...vell.com>
Subject: Re: [PATCH RFC xfrm-next v3 0/8] Extend XFRM core to allow full
offload configuration
On Sun, Sep 04, 2022 at 04:15:34PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.com>
<...>
> Leon Romanovsky (8):
> xfrm: add new full offload flag
> xfrm: allow state full offload mode
> xfrm: add an interface to offload policy
> xfrm: add TX datapath support for IPsec full offload mode
> xfrm: add RX datapath protection for IPsec full offload mode
> xfrm: enforce separation between priorities of HW/SW policies
> xfrm: add support to HW update soft and hard limits
> xfrm: document IPsec full offload mode
Kindly reminder.
Thanks
Powered by blists - more mailing lists