From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org, fsverity@lists.linux.dev,
dm-devel@lists.linux.dev
Cc: x86@kernel.org, linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v3 0/8] Optimize dm-verity and fsverity using multibuffer hashing
Date: Mon, 6 May 2024 17:23:35 -0700 [thread overview]
Message-ID: <20240507002343.239552-1-ebiggers@kernel.org> (raw)
On many modern CPUs, it is possible to compute the SHA-256 hash of two
equal-length messages in about the same time as a single message, if all
the instructions are interleaved. This is because each SHA-256 (and
also most other cryptographic hash functions) is inherently serialized
and therefore can't always take advantage of the CPU's full throughput.
An earlier attempt to support multibuffer hashing in Linux was based
around the ahash API. That approach had some major issues. This
patchset instead takes a much simpler approach of just adding a
synchronous API for hashing equal-length messages.
This works well for dm-verity and fsverity, which use Merkle trees and
therefore hash large numbers of equal-length messages.
This patchset is organized as follows:
- Patch 1-3 add crypto_shash_finup_mb() and tests for it.
- Patch 4-5 implement finup_mb on x86_64 and arm64, using an
interleaving factor of 2.
- Patch 6-8 update fsverity and dm-verity to use crypto_shash_finup_mb()
to hash pairs of data blocks when possible. Note: the patch
"dm-verity: hash blocks with shash import+finup when possible" is
revived from its original submission
(https://lore.kernel.org/dm-devel/20231030023351.6041-1-ebiggers@kernel.org/)
because this new work provides a new motivation for it.
On CPUs that support multiple concurrent SHA-256's (all arm64 CPUs I
tested, and AMD Zen CPUs), raw SHA-256 hashing throughput increases by
70-98%, and the throughput of cold-cache reads from dm-verity and
fsverity increases by very roughly 35%.
Changed in v3:
- Change API from finup2x to finup_mb. It now takes arrays of data
buffer and output buffers, avoiding hardcoding 2x in the API.
Changed in v2:
- Rebase onto cryptodev/master
- Add more comments to assembly
- Reorganize some of the assembly slightly
- Fix the claimed throughput improvement on arm64
- Fix incorrect kunmap order in fs/verity/verify.c
- Adjust testmgr generation logic slightly
- Explicitly check for INT_MAX before casting unsigned int to int
- Mention SHA3 based parallel hashes
- Mention AVX512-based approach
Eric Biggers (8):
crypto: shash - add support for finup_mb
crypto: testmgr - generate power-of-2 lengths more often
crypto: testmgr - add tests for finup_mb
crypto: x86/sha256-ni - add support for finup_mb
crypto: arm64/sha256-ce - add support for finup_mb
fsverity: improve performance by using multibuffer hashing
dm-verity: hash blocks with shash import+finup when possible
dm-verity: improve performance by using multibuffer hashing
arch/arm64/crypto/sha2-ce-core.S | 281 +++++++++++++-
arch/arm64/crypto/sha2-ce-glue.c | 40 ++
arch/x86/crypto/sha256_ni_asm.S | 368 ++++++++++++++++++
arch/x86/crypto/sha256_ssse3_glue.c | 39 ++
crypto/shash.c | 60 +++
crypto/testmgr.c | 91 ++++-
drivers/md/dm-verity-fec.c | 31 +-
drivers/md/dm-verity-fec.h | 7 +-
drivers/md/dm-verity-target.c | 563 ++++++++++++++++++++--------
drivers/md/dm-verity.h | 43 +--
fs/verity/fsverity_private.h | 5 +
fs/verity/hash_algs.c | 32 +-
fs/verity/open.c | 6 +
fs/verity/verify.c | 177 +++++++--
include/crypto/hash.h | 45 ++-
15 files changed, 1543 insertions(+), 245 deletions(-)
base-commit: ed265f7fd9a635d77c8022fc6d9a1b735dd4dfd7
--
2.45.0
next reply other threads:[~2024-05-07 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 0:23 Eric Biggers [this message]
2024-05-07 0:23 ` [PATCH v3 1/8] crypto: shash - add support for finup_mb Eric Biggers
2024-05-07 0:23 ` [PATCH v3 2/8] crypto: testmgr - generate power-of-2 lengths more often Eric Biggers
2024-05-07 0:23 ` [PATCH v3 3/8] crypto: testmgr - add tests for finup_mb Eric Biggers
2024-05-07 0:23 ` [PATCH v3 4/8] crypto: x86/sha256-ni - add support " Eric Biggers
2024-05-07 0:23 ` [PATCH v3 5/8] crypto: arm64/sha256-ce " Eric Biggers
2024-05-07 0:23 ` [PATCH v3 6/8] fsverity: improve performance by using multibuffer hashing Eric Biggers
2024-05-07 0:23 ` [PATCH v3 7/8] dm-verity: hash blocks with shash import+finup when possible Eric Biggers
2024-05-07 0:23 ` [PATCH v3 8/8] dm-verity: improve performance by using multibuffer hashing Eric Biggers
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=20240507002343.239552-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=bvanassche@acm.org \
--cc=dm-devel@lists.linux.dev \
--cc=fsverity@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=samitolvanen@google.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).