From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Stephan Müller" <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Decreasing time for `rsa_init`
Date: Wed, 12 Jul 2017 19:38:32 +0200 [thread overview]
Message-ID: <8d89fefa-b27d-ba32-e7b2-75312549ee90@molgen.mpg.de> (raw)
In-Reply-To: <3649766.4rHtxdK8Pi@tauon.chronox.de>
Dear Stephan,
Thank you for the quick response.
On 07/12/17 19:28, Stephan Müller wrote:
> Am Mittwoch, 12. Juli 2017, 12:59:58 CEST schrieb Paul Menzel:
>> Building CRYPTO_RSA not as module, but into the Linux kernel,
>> `rsa_init()` takes 130 ms on an ASRock E350M1.
>>
>> (Timings are shown by adding `initcall_debug` to Linux command line [1].
>> The times are visualized by `analyze_boot.py` from pm-graph [2] or
>> `systemd-bootchart`.)
>>
>> This is quite a lot of time compared to other modules, and I wonder if
>> there are ways to decrease that time other than building it as a module,
>> and not signing modules?
>
> Is the testmgr compiled? If yes, the self test may take that time.
It looks like it is, as the tests are not disabled.
```
$ grep MANAGER_DISABLE_TESTS .config
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
```
I’ll try an image without the tests, and will report back.
Kind regards,
Paul
>> [1] http://elinux.org/Initcall_Debug
>> [2] https://github.com/01org/pm-graph
next prev parent reply other threads:[~2017-07-12 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 10:59 Paul Menzel
2017-07-12 17:28 ` Stephan Müller
2017-07-12 17:38 ` Paul Menzel [this message]
2017-07-13 18:20 ` Paul Menzel
2017-12-26 8:28 ` Paul Menzel
2017-12-26 21:49 ` Randy Dunlap
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=8d89fefa-b27d-ba32-e7b2-75312549ee90@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/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
all inboxes | Powered by JetHome®