From: Ard Biesheuvel <ardb@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, Ard Biesheuvel <ardb@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
David Laight <David.Laight@aculab.com>
Subject: [PATCH 0/2] crypto: xor - defer and optimize boot time benchmark
Date: Wed, 23 Sep 2020 20:22:28 +0200 [thread overview]
Message-ID: <20200923182230.22715-1-ardb@kernel.org> (raw)
Doug reports [0] that the XOR boot time benchmark takes more time than
necessary, and runs at a time when there is little room for other
boot time tasks to run concurrently.
Let's fix this by #1 deferring the benchmark, and #2 uses a faster
implementation.
[0] https://lore.kernel.org/linux-arm-kernel/20200921172603.1.Id9450c1d3deef17718bd5368580a3c44895209ee@changeid/
Cc: Douglas Anderson <dianders@chromium.org>
Cc: David Laight <David.Laight@aculab.com>
Ard Biesheuvel (2):
crypto: xor - defer load time benchmark to a later time
crypto: xor - use ktime for template benchmarking
crypto/xor.c | 65 +++++++++++++-------
1 file changed, 43 insertions(+), 22 deletions(-)
--
2.17.1
next reply other threads:[~2020-09-23 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 18:22 Ard Biesheuvel [this message]
2020-09-23 18:22 ` [PATCH 1/2] crypto: xor - defer load time benchmark to a later time Ard Biesheuvel
2020-09-24 0:38 ` Doug Anderson
2020-09-23 18:22 ` [PATCH 2/2] crypto: xor - use ktime for template benchmarking Ard Biesheuvel
2020-09-24 0:36 ` Doug Anderson
2020-09-24 8:31 ` Ard Biesheuvel
2020-09-24 15:28 ` Doug Anderson
2020-09-24 15:36 ` Ard Biesheuvel
2020-09-24 18:22 ` Doug Anderson
2020-09-24 18:40 ` Ard Biesheuvel
2020-09-24 18:52 ` Doug Anderson
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=20200923182230.22715-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=David.Laight@aculab.com \
--cc=dianders@chromium.org \
--cc=herbert@gondor.apana.org.au \
--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.