Re: [Ocf-linux-users] AES hardware accelerator in OpenSSL with OCF

[Hector P. <hec...@di...>]

David McCullough wrote:
> 	insert aes module
> 	modprobe ocf
> 	modprobe cryptosoft swcr_debug=1
> 	modprobe cryptodev
> 	openssl speed -elapsed -evp aes
> 
> 	check kernel log/console output for crytosoft debug output.
> 
> If that works then there must be some way for you driver to take over
> cbc(aes) that you are missing.  Perhaps the normal crypto API SW driver
> is getting priority ?

Hi David,

I have seen that, if I load the kernel's aes_generic.ko and cbc.ko, then 
cryptosoft module reports that cbc(aes) algorithm is supported:
...
crypto_register(id=0x3, alg=11, maxoplen=0, flags=0x0)
...

and it eventually calls the kernel's aes_generic.c crypto functions 
(this seem to work, as you said). On the other hand, if I simply load my 
driver, cryptosoft reports that the cbc(aes) algorithm is not supported:

...
cryptosoft_init:BLKCIPHER algorithm 11:'cbc(aes)' not supported
...

I don't see many differences between the way aes_generic loads the 
algorithm and the way my driver does it. The main difference is that 
aes_generic cra_flags is CRYPTO_ALG_TYPE_CIPHER while my driver is 
CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_ASYNC.
In other words, my driver uses .cra_u.ablkcipher to define the crypto 
functions while the aes_generic uses .cra_u.cipher. Do you know if this 
makes any difference to OCF layer?
--
Hector Palacios