[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250217094032.3cbe64c7@kernel.org>
Date: Mon, 17 Feb 2025 09:40:32 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Eric Biggers <ebiggers@...nel.org>, fsverity@...ts.linux.dev,
linux-crypto@...r.kernel.org, dm-devel@...ts.linux.dev, x86@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Ard
Biesheuvel <ardb@...nel.org>, Sami Tolvanen <samitolvanen@...gle.com>,
Alasdair Kergon <agk@...hat.com>, Mike Snitzer <snitzer@...nel.org>, Linus
Torvalds <torvalds@...ux-foundation.org>, Mikulas Patocka
<mpatocka@...hat.com>, David Howells <dhowells@...hat.com>,
netdev@...r.kernel.org
Subject: Re: [PATCH v8 0/7] Optimize dm-verity and fsverity using
multibuffer hashing
On Sun, 16 Feb 2025 10:27:02 +0800 Herbert Xu wrote:
> On Sat, Feb 15, 2025 at 09:04:12AM -0800, Jakub Kicinski wrote:
> > Can confirm, FWIW. I don't know as much about IPsec, but for TLS
> > lightweight SW-only crypto would be ideal.
>
> Please note that while CPU-only crypto is the best for networking,
> it actually operates in asynchronous mode on x86. This is because
> RX occurs in softirq context, which may not be able to use SIMD on
> x86.
Yes, that's true for tunnels and for IPsec.
TLS does crypto in sendmsg/recvmsg, process context.
Powered by blists - more mailing lists