Re: [Ocf-linux-users] ocf seem not working

[David M. <dav...@mc...>]

Jivin Stefan Kuhne lays it down ...
> Hello,
> 
> I've got ofc and openssl build.
> Now i get:
> 
> Guardian 3.9.0-rev24403 # ./openssl speed -evp aes-128-cbc -engine cryptodev
> engine "cryptodev" set.
> Doing aes-128-cbc for 3s on 16 size blocks: 862864 aes-128-cbc's in 2.97s
> Doing aes-128-cbc for 3s on 64 size blocks: 246323 aes-128-cbc's in 2.93s
> Doing aes-128-cbc for 3s on 256 size blocks: 61891 aes-128-cbc's in 2.85s
> Doing aes-128-cbc for 3s on 1024 size blocks: 16226 aes-128-cbc's in 2.96s
> Doing aes-128-cbc for 3s on 8192 size blocks: 2022 aes-128-cbc's in 2.91s
> OpenSSL 1.0.0j 10 May 2012
> built on: date not available
> options:bn(64,32) rc4(ptr,char) des(idx,cisc,16,long) aes(partial)
> blowfish(ptr)
> compiler: i586-unknown-linux-uclibc-gcc -fPIC -DOPENSSL_PIC
> -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
> -DHAVE_DLFCN_H -DTERMIO  -pipe -Os -g2 -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -fno-unwind-tables
> -fno-asynchronous-unwind-tables -DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS
> -fomit-frame-pointer -Wall
> The 'numbers' are in 1000s of bytes per second processed.
> type             16 bytes     64 bytes    256 bytes   1024 bytes   8192
> bytes
> aes-128-cbc       4648.43k     5380.43k     5559.33k     5613.32k
> 5692.17k
> Guardian 3.9.0-rev24403 # lsmod
> ...
> cryptosoft             16461  0
> geode_aes              12337  2
> cryptodev              16433  4
> ocf                    21404  2 cryptosoft,cryptodev
> cs5535_mfd             12337  0
> aes_i586               16567  2
> aes_generic            36986  1 aes_i586
> ...
> Guardian 3.9.0-rev24403 # openssl engine
> (cryptodev) BSD cryptodev engine
> (dynamic) Dynamic engine loading support
> Guardian 3.9.0-rev24403 #
> 
> It seems, that ocf doesn't work.
> Any ideas were I can work on?


Get the cryptotest program from the ocf tarball and compile and run that.
It talk directly to /dev/crypto and will confirm that you have everything
else working.  It can also do speed tests.

Once you get that working,  then try:

	openssl speed -engine cryptodev -evp aes128 -elapsed

You really need to run "openssl speed" with -elapsed to get real useful
numbers out IMO.

If that doesn't appear to be working,  try enabling debug in both the
cryptodev/cryptosoft drivers to see what they can tell you.  Debug(kernel
console output) will tell you if they are being accessed and may helkp track
any failures,

Cheers,
Davidm

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