summaryrefslogtreecommitdiff
path: root/crypto/Kconfig
diff options
context:
space:
mode:
authorHerbert Xu <herbert@gondor.apana.org.au>2005-11-05 16:58:14 +1100
committerDavid S. Miller <davem@sunset.davemloft.net>2006-01-09 14:15:37 -0800
commitbfdc4ac1ca69d010637d4dd77cffd39e26a3463b (patch)
treebf70ebc2911e1678907a3d6f4141534e619ac075 /crypto/Kconfig
parentcbbf485e2e5d835229d210c9e91cff4e7fdc63f9 (diff)
downloadlinux-crypto-bfdc4ac1ca69d010637d4dd77cffd39e26a3463b.tar.gz
linux-crypto-bfdc4ac1ca69d010637d4dd77cffd39e26a3463b.zip
[CRYPTO] Allow multiple implementations of the same algorithm
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>
Diffstat (limited to 'crypto/Kconfig')
0 files changed, 0 insertions, 0 deletions