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

[David M. <Dav...@se...>]

Jivin Hector Palacios lays it down ...
> David McCullough wrote:
> >What functions does you driver provide ?  You can see the list that
> >cryptosoft in the crypto_details table in cryptosoft.c  
> 
> My driver provides cbc(aes) and ecb(aes) encryption algorithms for 128, 
> 192, and 256 key lengths.
> The crypto_details table in cryptosoft lists cbc(aes) among others, but 
> not ecb(aes).
> Does this table list the software algorithms provided by OCF?

No,  just the ones supported by the cryptosoft driver,  which is basically
an OCF to cryptoAPI wrapper.

> Must I include somehow my algorithms to this list? Or at least ecb(aes)?

Most of the OCF supported algs are already in there,  so probably not.

OCF doesn't current support ECB algs (at least I don't see it).

> > I am not an
> > expert on how the kernel crypto API matches up cbc(aes) to a driver
> > so I can't help you there.
> 
> Thanks anyway.

Try putting the kernel AES module in,  turning on debug in the
cryptosoft driver and see if that is getting used:

	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 ?

Cheers,
Davidm

-- 
David McCullough,  dav...@se...,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org   http://www.snapgear.com