From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932407AbdGLLAE (ORCPT ); Wed, 12 Jul 2017 07:00:04 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:50000 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756559AbdGLLAB (ORCPT ); Wed, 12 Jul 2017 07:00:01 -0400 To: linux-crypto@vger.kernel.org Cc: linux-kernel@vger.kernel.org From: Paul Menzel Subject: Decreasing time for `rsa_init` Message-ID: <4ec5a3f5-9605-cdcd-23cf-1df7b3af211c@molgen.mpg.de> Date: Wed, 12 Jul 2017 12:59:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Linux crypto folks, 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? Kind regards, Paul [1] http://elinux.org/Initcall_Debug [2] https://github.com/01org/pm-graph