diff options
author | Robert Elliott <elliott@hpe.com> | 2022-08-13 18:04:31 -0500 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2022-08-19 18:39:39 +0800 |
commit | aa031b8f702e7941b4c86022348a366c335d389a (patch) | |
tree | 0182a578d0b37f1308e90e322cea93e042dfd9e6 /crypto/testmgr.c | |
parent | 6a088a2cbcaf40747cf2881df47f4f5d65acd7ab (diff) | |
download | linux-aa031b8f702e7941b4c86022348a366c335d389a.tar.gz linux-aa031b8f702e7941b4c86022348a366c335d389a.tar.bz2 linux-aa031b8f702e7941b4c86022348a366c335d389a.zip |
crypto: x86/sha512 - load based on CPU features
x86 optimized crypto modules built as modules rather than built-in
to the kernel end up as .ko files in the filesystem, e.g., in
/usr/lib/modules. If the filesystem itself is a module, these might
not be available when the crypto API is initialized, resulting in
the generic implementation being used (e.g., sha512_transform rather
than sha512_transform_avx2).
In one test case, CPU utilization in the sha512 function dropped
from 15.34% to 7.18% after forcing loading of the optimized module.
Add module aliases for this x86 optimized crypto module based on CPU
feature bits so udev gets a chance to load them later in the boot
process when the filesystems are all running.
Signed-off-by: Robert Elliott <elliott@hpe.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/testmgr.c')
0 files changed, 0 insertions, 0 deletions