From: Jakub Kicinski <kuba@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Eric Biggers <ebiggers@kernel.org>,
fsverity@lists.linux.dev, linux-crypto@vger.kernel.org,
dm-devel@lists.linux.dev, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mikulas Patocka <mpatocka@redhat.com>,
David Howells <dhowells@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v8 0/7] Optimize dm-verity and fsverity using multibuffer hashing
Date: Mon, 17 Feb 2025 09:40:32 -0800 [thread overview]
Message-ID: <20250217094032.3cbe64c7@kernel.org> (raw)
In-Reply-To: <Z7FM9rhEA7n476EJ@gondor.apana.org.au>
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.
next prev parent reply other threads:[~2025-02-17 17:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 15:47 [PATCH v8 0/7] Optimize dm-verity and fsverity using multibuffer hashing Eric Biggers
2025-02-12 15:47 ` [PATCH v8 1/7] crypto: shash - add support for finup_mb Eric Biggers
2025-02-12 15:47 ` [PATCH v8 2/7] crypto: testmgr - add tests " Eric Biggers
2025-02-12 15:47 ` [PATCH v8 3/7] crypto: x86/sha256-ni - add support " Eric Biggers
2025-02-12 15:47 ` [PATCH v8 4/7] crypto: arm64/sha256-ce " Eric Biggers
2025-02-12 15:47 ` [PATCH v8 5/7] fsverity: improve performance by using multibuffer hashing Eric Biggers
2025-02-12 15:47 ` [PATCH v8 6/7] dm-verity: reduce scope of real and wanted digests Eric Biggers
2025-02-12 15:47 ` [PATCH v8 7/7] dm-verity: improve performance by using multibuffer hashing Eric Biggers
2025-02-13 4:17 ` [PATCH v8 0/7] Optimize dm-verity and fsverity " Herbert Xu
2025-02-13 6:33 ` Eric Biggers
2025-02-14 2:44 ` Herbert Xu
2025-02-14 3:35 ` Eric Biggers
2025-02-14 3:50 ` Herbert Xu
2025-02-14 4:29 ` Eric Biggers
2025-02-14 4:56 ` Herbert Xu
2025-02-14 6:11 ` Eric Biggers
2025-02-14 10:50 ` Ard Biesheuvel
2025-02-15 17:04 ` Jakub Kicinski
2025-02-16 2:27 ` Herbert Xu
2025-02-16 3:26 ` Eric Biggers
2025-02-16 3:29 ` Herbert Xu
2025-02-17 17:40 ` Jakub Kicinski [this message]
2025-02-18 3:42 ` Herbert Xu
2025-02-18 7:41 ` Ard Biesheuvel
2025-02-18 8:02 ` Herbert Xu
2025-02-13 10:10 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250217094032.3cbe64c7@kernel.org \
--to=kuba@kernel.org \
--cc=agk@redhat.com \
--cc=ardb@kernel.org \
--cc=dhowells@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=snitzer@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.