Re: [Ocf-linux-users] ocf seem not working
Brought to you by:
david-m
From: David M. <dav...@mc...> - 2012-12-12 23:47:07
|
Jivin Stefan Kuhne lays it down ... > Am 12.12.2012 01:24, schrieb David McCullough: > > Hello, > > > That looks right to me. You can tell you are using HW crypto because the > > speed throughput increases significantly with the packet size. Unfortunately > > passing data to the kernel and back for crypto is not ideal :-( > > > but I gt with and without "-engine cryptodev" the same result: Ok, I wasn't sure you were seeing that. I was pretty sure that cryptodev will be used by default these days (old versions didn't do this). Specifying it makes sure yuo have the best chance ;-) Cheers, Davidm > > Guardian 3.9.0-rev24485 # openssl speed -engine cryptodev -evp aes128 > -elapsed > engine "cryptodev" set. > You have chosen to measure elapsed time instead of user CPU time. > Doing aes-128-cbc for 3s on 16 size blocks: 111539 aes-128-cbc's in 3.02s > Doing aes-128-cbc for 3s on 64 size blocks: 103749 aes-128-cbc's in 3.01s > Doing aes-128-cbc for 3s on 256 size blocks: 98841 aes-128-cbc's in 3.02s > Doing aes-128-cbc for 3s on 1024 size blocks: 62480 aes-128-cbc's in 3.02s > Doing aes-128-cbc for 3s on 8192 size blocks: 15896 aes-128-cbc's in 3.02s > 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 590.94k 2205.96k 8378.57k 21185.27k > 43119.22k > Guardian 3.9.0-rev24485 # openssl speed -evp aes128 -elapsed > You have chosen to measure elapsed time instead of user CPU time. > Doing aes-128-cbc for 3s on 16 size blocks: 113714 aes-128-cbc's in 3.01s > Doing aes-128-cbc for 3s on 64 size blocks: 111686 aes-128-cbc's in 3.01s > Doing aes-128-cbc for 3s on 256 size blocks: 93473 aes-128-cbc's in 3.01s > Doing aes-128-cbc for 3s on 1024 size blocks: 65328 aes-128-cbc's in 3.01s > Doing aes-128-cbc for 3s on 8192 size blocks: 15566 aes-128-cbc's in 3.01s > 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 604.46k 2374.72k 7949.86k 22224.54k > 42364.34k > Guardian 3.9.0-rev24485 # > > Is this option obsolete? > > Regards, > Stefan Kuhne > > > > Content-Type: multipart/signed; micalg=pgp-sha1; > protocol="application/pgp-signature"; > boundary="------------enig5ABF492CECA018A510CB137F" > > --------------enig5ABF492CECA018A510CB137F > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > Am 12.12.2012 01:24, schrieb David McCullough: > > Hello, > > > That looks right to me. You can tell you are using HW crypto because t= > he > > speed throughput increases significantly with the packet size. Unfort= > unately > > passing data to the kernel and back for crypto is not ideal :-( > >=20 > but I gt with and without "-engine cryptodev" the same result: > > Guardian 3.9.0-rev24485 # openssl speed -engine cryptodev -evp aes128 > -elapsed > engine "cryptodev" set. > You have chosen to measure elapsed time instead of user CPU time. > Doing aes-128-cbc for 3s on 16 size blocks: 111539 aes-128-cbc's in 3.02s= > > Doing aes-128-cbc for 3s on 64 size blocks: 103749 aes-128-cbc's in 3.01s= > > Doing aes-128-cbc for 3s on 256 size blocks: 98841 aes-128-cbc's in 3.02s= > > Doing aes-128-cbc for 3s on 1024 size blocks: 62480 aes-128-cbc's in 3.02= > s > Doing aes-128-cbc for 3s on 8192 size blocks: 15896 aes-128-cbc's in 3.02= > s > 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=3D64 -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 590.94k 2205.96k 8378.57k 21185.27k > 43119.22k > Guardian 3.9.0-rev24485 # openssl speed -evp aes128 -elapsed > You have chosen to measure elapsed time instead of user CPU time. > Doing aes-128-cbc for 3s on 16 size blocks: 113714 aes-128-cbc's in 3.01s= > > Doing aes-128-cbc for 3s on 64 size blocks: 111686 aes-128-cbc's in 3.01s= > > Doing aes-128-cbc for 3s on 256 size blocks: 93473 aes-128-cbc's in 3.01s= > > Doing aes-128-cbc for 3s on 1024 size blocks: 65328 aes-128-cbc's in 3.01= > s > Doing aes-128-cbc for 3s on 8192 size blocks: 15566 aes-128-cbc's in 3.01= > s > 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=3D64 -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 604.46k 2374.72k 7949.86k 22224.54k > 42364.34k > Guardian 3.9.0-rev24485 # > > Is this option obsolete? > > Regards, > Stefan Kuhne > > > > --------------enig5ABF492CECA018A510CB137F > Content-Type: application/pgp-signature; name="signature.asc" > Content-Description: OpenPGP digital signature > Content-Disposition: attachment; filename="signature.asc" > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.17 (MingW32) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJQyMZpAAoJEFLNPgL3IBVXCjAH/RmEOfoyV5LC+jrHRSeqYtXO > KwWX16Z1eSp85IqK8HlL9xA/QhrHvrvFKZNbmu7IPIFSuLdNxLrqteq5vGNU9kcl > BRgkJmhSZK5Mjd7yLWwNccFcyhP/buR0f+H5drfPesDybRTyDwASdWmw6oRAuU3c > 6UrPoBomx7n0rt45OgYHV6+CUglv7Urb6Jzr08plWmreayFhvajQTMVLBXf6cOIN > RIS7ewgLpmXo8ZXtruXo59KQOQ3GvU5HKa3hGXLWYZfKud84l+ZKP7U4WYKmzHgK > hSHmO6AJ/2Bux83kWBvd9QYuTOYO+Wu6BXtvf9MPNMsLvnvspkATeD0TLVPv57c= > =lt03 > -----END PGP SIGNATURE----- > > --------------enig5ABF492CECA018A510CB137F-- -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |