Re: [Ocf-linux-users] hardware acceleration question

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

Jivin Max lays it down ...
> Hello.
> 
> I'm using ocf with pretty old kernel 2.6.12 to get hardware acceleration
> working with Micronas chips.
> 
> After compilation I got following:
> 
> openssl engine
> Hardware
> cryptodev RSA
> cryptodev DSA
> cryptodev DH
> eng_cryptodev.c:1334 CIOCASYMFEAT - failure
> (cryptodev) BSD cryptodev engine
> (dynamic) Dynamic engine loading support
> 
> ~ # cat /proc/crypto
> name         : aes
> module       : kernel
> type         : cipher
> blocksize    : 16
> min keysize  : 16
> max keysize  : 32
> 
> name         : crc32c
> module       : kernel
> type         : digest
> blocksize    : 32
> digestsize   : 4
> 
> It looks like ocf itself is loaded (/dev/crypto is present) but
> appropriate drivers are not. However I see messages from these drivers
> in dmesg:
> 
> ~ # dmesg |grep AES
> 7108: AES @ 0xbb500100 (0x1b500100 phys) CTR mode
> 8100: AES @ 0xb8500000 (0x18500000 phys) ctr mode
> 
> This looks confusing: how can I make sure that particular driver is
> loaded and will be use by openssl?
> If it's not loaded\used - what should I do to track problem?

/proc/crypto is not part of OCF,  that is the kernel crypto API.

Have you loaded the OCF modules (or compiled them into your kernel ?)

You will need at least three drivers loaded, for example:

	ocf 15616 3 cryptodev,ixp4xx, Live 0xc3d58000 (P)
	cryptodev 10180 0 - Live 0xc3d80000 (P)
	ixp4xx 7152 0 - Live 0xc3d74000

The drivers are:

	ocf       - the main ocf core
	cryptodev - the interface needed for user space access
	ixp4xx    - the ocf HW driver for this device,  you may have a different
	            one (safe/hifn/talitos/...) or use the SW version,
				cryptosoft.

If you use cryptosoft,  you need to add more algorithms to your kernel
crypto config for it to be of much use.

Cheers,
Davidm

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