From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Subject: [PATCH v2 0/6] crypto: reduce overhead when self-tests disabled
Date: Thu, 10 Nov 2022 00:13:40 -0800 [thread overview]
Message-ID: <20221110081346.336046-1-ebiggers@kernel.org> (raw)
This patchset makes it so that the self-test code doesn't still slow
things down when self-tests are disabled via the kconfig.
It also optimizes the registration of "internal" algorithms and silences
a noisy log message.
Eric Biggers (6):
crypto: optimize algorithm registration when self-tests disabled
crypto: optimize registration of internal algorithms
crypto: compile out crypto_boot_test_finished when tests disabled
crypto: skip kdf_sp800108 self-test when tests disabled
crypto: silence noisy kdf_sp800108 self-test
crypto: compile out test-related algboss code when tests disabled
crypto/algapi.c | 160 ++++++++++++++++++++++++------------------
crypto/algboss.c | 26 +++----
crypto/api.c | 8 ++-
crypto/internal.h | 13 +++-
crypto/kdf_sp800108.c | 11 ++-
5 files changed, 124 insertions(+), 94 deletions(-)
base-commit: f67dd6ce0723ad013395f20a3f79d8a437d3f455
--
2.38.1
next reply other threads:[~2022-11-10 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 8:13 Eric Biggers [this message]
2022-11-10 8:13 ` [PATCH v2 1/6] crypto: optimize algorithm registration when self-tests disabled Eric Biggers
2022-11-10 19:42 ` Eric Biggers
2022-11-11 4:06 ` Herbert Xu
2022-11-10 8:13 ` [PATCH v2 2/6] crypto: optimize registration of internal algorithms Eric Biggers
2022-11-10 8:13 ` [PATCH v2 3/6] crypto: compile out crypto_boot_test_finished when tests disabled Eric Biggers
2022-11-10 8:13 ` [PATCH v2 4/6] crypto: skip kdf_sp800108 self-test " Eric Biggers
2022-11-10 8:13 ` [PATCH v2 5/6] crypto: silence noisy kdf_sp800108 self-test Eric Biggers
2022-11-10 8:13 ` [PATCH v2 6/6] crypto: compile out test-related algboss code when tests disabled Eric Biggers
2022-11-11 4:14 ` Herbert Xu
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=20221110081346.336046-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.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.