[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aEGW_5HfPqU1rFjl@krikkit>
Date: Thu, 5 Jun 2025 15:09:19 +0200
From: Sabrina Dubroca <sd@...asysnail.net>
To: Steffen Klassert <steffen.klassert@...unet.com>,
Leon Romanovsky <leon@...nel.org>
Cc: Leon Romanovsky <leonro@...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>
Subject: Re: [PATCH ipsec-next v1 1/5] xfrm: delay initialization of offload
path till its actually requested
Hello,
I think we need to revert this patch. It causes a severe performance
regression for SW IPsec (around 40-50%).
2025-02-19, 15:50:57 +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.com>
>
> XFRM offload path is probed even if offload isn't needed at all. Let's
> make sure that x->type_offload pointer stays NULL for such path to
> reduce ambiguity.
x->type_offload is used for GRO with SW IPsec, not just for HW offload.
--
Sabrina
Powered by blists - more mailing lists