crypto: sha1_generic - add cra_priority
sha1-generic had a cra_priority of 0, so it wasn't possible to have a lower priority SHA-1 implementation, as is desired for sha1_mb which is only useful under certain workloads and is otherwise extremely slow. Change it to priority 100, which is the priority used for many of the other generic algorithms. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
This commit is contained in:
parent
26ec38872b
commit
90ef3e4835
|
@ -76,6 +76,7 @@ static struct shash_alg alg = {
|
||||||
.base = {
|
.base = {
|
||||||
.cra_name = "sha1",
|
.cra_name = "sha1",
|
||||||
.cra_driver_name= "sha1-generic",
|
.cra_driver_name= "sha1-generic",
|
||||||
|
.cra_priority = 100,
|
||||||
.cra_flags = CRYPTO_ALG_TYPE_SHASH,
|
.cra_flags = CRYPTO_ALG_TYPE_SHASH,
|
||||||
.cra_blocksize = SHA1_BLOCK_SIZE,
|
.cra_blocksize = SHA1_BLOCK_SIZE,
|
||||||
.cra_module = THIS_MODULE,
|
.cra_module = THIS_MODULE,
|
||||||
|
|
Loading…
Reference in New Issue