Re: [Ocf-linux-users] ocf seem not working
Brought to you by:
david-m
From: Stefan K. <ste...@gm...> - 2012-12-11 15:57:06
|
Am 06.12.2012 13:15, schrieb David McCullough: Hello, I've found some time for testing: Guardian 3.9.0-rev24485 # ./cryptotest -z 0.000 sec, 2 aes crypts, 16 bytes, 340426 byte/sec, 2.6 Mb/sec 0.000 sec, 2 aes crypts, 32 bytes, 800000 byte/sec, 6.1 Mb/sec 0.000 sec, 2 aes crypts, 64 bytes, 1641026 byte/sec, 12.5 Mb/sec 0.000 sec, 2 aes crypts, 128 bytes, 3084337 byte/sec, 23.5 Mb/sec 0.000 sec, 2 aes crypts, 256 bytes, 6023529 byte/sec, 46.0 Mb/sec 0.000 sec, 2 aes crypts, 512 bytes, 10343434 byte/sec, 78.9 Mb/sec 0.000 sec, 2 aes crypts, 1024 bytes, 17808696 byte/sec, 135.9 Mb/sec 0.000 sec, 2 aes crypts, 2048 bytes, 25283951 byte/sec, 192.9 Mb/sec 0.000 sec, 2 aes crypts, 4096 bytes, 34565401 byte/sec, 263.7 Mb/sec 0.000 sec, 2 aes crypts, 8192 bytes, 38370023 byte/sec, 292.7 Mb/sec 0.001 sec, 2 aes crypts, 16384 bytes, 39479518 byte/sec, 301.2 Mb/sec 0.002 sec, 2 aes crypts, 32768 bytes, 43343915 byte/sec, 330.7 Mb/sec 0.005 sec, 2 aes crypts, 65280 bytes, 26693928 byte/sec, 203.7 Mb/sec 0.000 sec, 2 aes192 crypts, 16 bytes, 280702 byte/sec, 2.1 Mb/sec 0.000 sec, 2 aes192 crypts, 32 bytes, 659794 byte/sec, 5.0 Mb/sec 0.000 sec, 2 aes192 crypts, 64 bytes, 1142857 byte/sec, 8.7 Mb/sec 0.001 sec, 2 aes192 crypts, 128 bytes, 257028 byte/sec, 2.0 Mb/sec 0.000 sec, 2 aes192 crypts, 256 bytes, 2694737 byte/sec, 20.6 Mb/sec 0.000 sec, 2 aes192 crypts, 512 bytes, 3835206 byte/sec, 29.3 Mb/sec 0.000 sec, 2 aes192 crypts, 1024 bytes, 5550136 byte/sec, 42.3 Mb/sec 0.001 sec, 2 aes192 crypts, 2048 bytes, 6470774 byte/sec, 49.4 Mb/sec 0.001 sec, 2 aes192 crypts, 4096 bytes, 6895623 byte/sec, 52.6 Mb/sec 0.002 sec, 2 aes192 crypts, 8192 bytes, 7098787 byte/sec, 54.2 Mb/sec 0.005 sec, 2 aes192 crypts, 16384 bytes, 7170241 byte/sec, 54.7 Mb/sec 0.009 sec, 2 aes192 crypts, 32768 bytes, 7323276 byte/sec, 55.9 Mb/sec 0.018 sec, 2 aes192 crypts, 65280 bytes, 7177176 byte/sec, 54.8 Mb/sec 0.000 sec, 2 aes256 crypts, 16 bytes, 296296 byte/sec, 2.3 Mb/sec 0.000 sec, 2 aes256 crypts, 32 bytes, 640000 byte/sec, 4.9 Mb/sec 0.000 sec, 2 aes256 crypts, 64 bytes, 1219048 byte/sec, 9.3 Mb/sec 0.000 sec, 2 aes256 crypts, 128 bytes, 1969231 byte/sec, 15.0 Mb/sec 0.000 sec, 2 aes256 crypts, 256 bytes, 3180124 byte/sec, 24.3 Mb/sec 0.000 sec, 2 aes256 crypts, 512 bytes, 4112450 byte/sec, 31.4 Mb/sec 0.000 sec, 2 aes256 crypts, 1024 bytes, 5211196 byte/sec, 39.8 Mb/sec 0.001 sec, 2 aes256 crypts, 2048 bytes, 5801700 byte/sec, 44.3 Mb/sec 0.001 sec, 2 aes256 crypts, 4096 bytes, 6229658 byte/sec, 47.5 Mb/sec 0.003 sec, 2 aes256 crypts, 8192 bytes, 6387524 byte/sec, 48.7 Mb/sec 0.005 sec, 2 aes256 crypts, 16384 bytes, 6405004 byte/sec, 48.9 Mb/sec 0.010 sec, 2 aes256 crypts, 32768 bytes, 6506751 byte/sec, 49.6 Mb/sec 0.020 sec, 2 aes256 crypts, 65280 bytes, 6477476 byte/sec, 49.4 Mb/sec 0.000 sec, 2 arc4 crypts, 8 bytes, 137931 byte/sec, 1.1 Mb/sec 0.000 sec, 2 arc4 crypts, 16 bytes, 329897 byte/sec, 2.5 Mb/sec 0.000 sec, 2 arc4 crypts, 32 bytes, 609524 byte/sec, 4.7 Mb/sec 0.000 sec, 2 arc4 crypts, 64 bytes, 1242718 byte/sec, 9.5 Mb/sec 0.000 sec, 2 arc4 crypts, 128 bytes, 2133333 byte/sec, 16.3 Mb/sec 0.000 sec, 2 arc4 crypts, 256 bytes, 3764706 byte/sec, 28.7 Mb/sec 0.000 sec, 2 arc4 crypts, 512 bytes, 5657459 byte/sec, 43.2 Mb/sec 0.000 sec, 2 arc4 crypts, 1024 bytes, 7937984 byte/sec, 60.6 Mb/sec 0.000 sec, 2 arc4 crypts, 2048 bytes, 9547786 byte/sec, 72.8 Mb/sec 0.001 sec, 2 arc4 crypts, 4096 bytes, 10908123 byte/sec, 83.2 Mb/sec 0.001 sec, 2 arc4 crypts, 8192 bytes, 11252747 byte/sec, 85.9 Mb/sec 0.003 sec, 2 arc4 crypts, 16384 bytes, 11770115 byte/sec, 89.8 Mb/sec 0.005 sec, 2 arc4 crypts, 32768 bytes, 12109387 byte/sec, 92.4 Mb/sec 0.011 sec, 2 arc4 crypts, 65280 bytes, 12146246 byte/sec, 92.7 Mb/sec 0.000 sec, 1 md5 crypts, 8 bytes, 135593 byte/sec, 1.0 Mb/sec 0.000 sec, 1 md5 crypts, 16 bytes, 340426 byte/sec, 2.6 Mb/sec 0.000 sec, 1 md5 crypts, 32 bytes, 603774 byte/sec, 4.6 Mb/sec 0.000 sec, 1 md5 crypts, 64 bytes, 1280000 byte/sec, 9.8 Mb/sec 0.000 sec, 1 md5 crypts, 128 bytes, 2245614 byte/sec, 17.1 Mb/sec 0.000 sec, 1 md5 crypts, 256 bytes, 4654545 byte/sec, 35.5 Mb/sec 0.000 sec, 1 md5 crypts, 512 bytes, 7420290 byte/sec, 56.6 Mb/sec 0.000 sec, 1 md5 crypts, 1024 bytes, 13298701 byte/sec, 101.5 Mb/sec 0.000 sec, 1 md5 crypts, 2048 bytes, 17808696 byte/sec, 135.9 Mb/sec 0.000 sec, 1 md5 crypts, 4096 bytes, 24236686 byte/sec, 184.9 Mb/sec 0.000 sec, 1 md5 crypts, 8192 bytes, 26425806 byte/sec, 201.6 Mb/sec 0.001 sec, 1 md5 crypts, 16384 bytes, 29414722 byte/sec, 224.4 Mb/sec 0.001 sec, 1 md5 crypts, 32768 bytes, 30854991 byte/sec, 235.4 Mb/sec 0.002 sec, 1 md5 crypts, 65280 bytes, 31984321 byte/sec, 244.0 Mb/sec Guardian 3.9.0-rev24485 # This seams to be good. > openssl speed -engine cryptodev -evp aes128 -elapsed > 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: 114524 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 64 size blocks: 103451 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 256 size blocks: 96658 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 1024 size blocks: 59689 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 8192 size blocks: 15119 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 608.77k 2199.62k 8220.75k 20306.16k 41147.79k Guardian 3.9.0-rev24485 # This doesn't lock so good. Next step is to rebuild kernel with debug. Regards, Stefan Kuhne |