5cb1454b86
This is the first step on the road towards asynchronous support in the Crypto API. It adds support for having multiple crypto_alg objects for the same algorithm registered in the system. For example, each device driver would register a crypto_alg object for each algorithm that it supports. While at the same time the user may load software implementations of those same algorithms. Users of the Crypto API may then select a specific implementation by name, or choose any implementation for a given algorithm with the highest priority. The priority field is a 32-bit signed integer. In future it will be possible to modify it from user-space. This also provides a solution to the problem of selecting amongst various AES implementations, that is, aes vs. aes-i586 vs. aes-padlock. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> |
||
---|---|---|
.. | ||
aes.c | ||
anubis.c | ||
api.c | ||
arc4.c | ||
blowfish.c | ||
cast5.c | ||
cast6.c | ||
cipher.c | ||
compress.c | ||
crc32c.c | ||
crypto_null.c | ||
deflate.c | ||
des.c | ||
digest.c | ||
hmac.c | ||
internal.h | ||
Kconfig | ||
khazad.c | ||
Makefile | ||
md4.c | ||
md5.c | ||
michael_mic.c | ||
proc.c | ||
scatterwalk.c | ||
scatterwalk.h | ||
serpent.c | ||
sha1.c | ||
sha256.c | ||
sha512.c | ||
tcrypt.c | ||
tcrypt.h | ||
tea.c | ||
tgr192.c | ||
twofish.c | ||
wp512.c |