From: Jakub Kicinski <kuba@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
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: Sat, 15 Feb 2025 09:04:12 -0800 [thread overview]
Message-ID: <20250215090412.46937c11@kernel.org> (raw)
In-Reply-To: <20250213063304.GA11664@sol.localdomain>
On Wed, 12 Feb 2025 22:33:04 -0800 Eric Biggers wrote:
> So anyone who cares about TLS or IPsec performance should of course be using
> AES-GCM, as it's the fastest by far, and it has no need for multibuffer.
Can confirm, FWIW. I don't know as much about IPsec, but for TLS
lightweight SW-only crypto would be ideal.
next prev parent reply other threads:[~2025-02-15 17:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250212154718.44255-1-ebiggers@kernel.org>
2025-02-13 4:17 ` [PATCH v8 0/7] Optimize dm-verity and fsverity using multibuffer hashing 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 [this message]
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
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=20250215090412.46937c11@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).