Thread: [Ocf-linux-users] ocf seem not working
Brought to you by:
david-m
From: Stefan K. <ste...@gm...> - 2012-12-04 22:10:38
Attachments:
signature.asc
|
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? Regards, Stefan Kuhne |
From: David M. <dav...@mc...> - 2012-12-06 12:31:35
|
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 |
From: Stefan K. <ste...@gm...> - 2012-12-06 14:09:48
|
Am Do, 6.12.2012, 13:15 schrieb David McCullough: Hello, > 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. > I'll test it. > 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, > I found that the cbc module was missing. Now openssl shows more speed. But my openVPN connection has only 50% lesser CPU load. In the next days I'll test it with the cryptodev tool and an better meaurment system. Regards, Stefan Kuhne |
From: Stefan K. <ste...@gm...> - 2012-12-22 20:22:24
Attachments:
signature.asc
|
Am 15.12.2012 15:06, schrieb Stefan Kuhne: Hello, > I don't know if I told it. It's a board like Alix with AMD Geode CPU. > when I turn off my Atheros WLAN (with unload modules) I get 2.5 MByte/s over SMB. PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND 5580 1 root R 2848 1.1 0 86.0 openvpn --config /etc/openvpn/Bloebl.conf --daemon openvpn-Bloebl --management-hold 1470 2 root SW 0 0.0 0 6.6 [ocf_0] Could ocf use the AES engine of my Atheros WLAN card? cryptotest has an option "-d". Where can I get the possibly devices? Is there a defined module load order? Regards, Stefan Kuhne |
From: David M. <uc...@gm...> - 2012-12-26 23:11:48
|
Stefan Kuhne wrote the following: > Am 15.12.2012 15:06, schrieb Stefan Kuhne: > > Hello, > > > I don't know if I told it. It's a board like Alix with AMD Geode CPU. > > > when I turn off my Atheros WLAN (with unload modules) I get 2.5 MByte/s > over SMB. > > PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND > 5580 1 root R 2848 1.1 0 86.0 openvpn --config > /etc/openvpn/Bloebl.conf --daemon openvpn-Bloebl --management-hold > 1470 2 root SW 0 0.0 0 6.6 [ocf_0] > > Could ocf use the AES engine of my Atheros WLAN card? > cryptotest has an option "-d". Where can I get the possibly devices? > Is there a defined module load order? The -d option selects from OCF drivers. If you have an OCF driver or a linux driver (that can be used via cryptosoft), then you can use if with OCF. I haven't seen any mention of using the crypto in a WLAN card. Depending on how the API looks for this device it just might not be possible, Cheers, Davidm -- David McCullough, da...@sp..., Ph: 0410 560 763 |
From: Stefan K. <ste...@gm...> - 2012-12-11 15:57:06
Attachments:
signature.asc
|
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 |
From: Stefan K. <ste...@gm...> - 2012-12-11 18:42:46
Attachments:
signature.asc
|
Am 11.12.2012 16:56, schrieb Stefan Kuhne: Hello, > Next step is to rebuild kernel with debug. > anything else use ocf already. So dmesg is full with debug output even I doesn't run anything. Regards, Stefan Kuhne |
From: Stefan K. <ste...@gm...> - 2012-12-12 18:13:21
Attachments:
signature.asc
|
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: 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 |
From: Stefan K. <ste...@gm...> - 2012-12-27 00:17:27
Attachments:
signature.asc
|
Am 26.12.2012 23:55, schrieb David McCullough: Hallo, > The -d option selects from OCF drivers. > > If you have an OCF driver or a linux driver (that can be used via > cryptosoft), then you can use if with OCF. > ah, ok. I use cryptosoft with geode-aes. > I haven't seen any mention of using the crypto in a WLAN card. > Depending on how the API looks for this device it just might not be > possible, > It was a idea but it seems, that SMB has 2,5MByte/s in all configs. Thanks for your help and regards, Stefan Kuhne |
From: David M. <uc...@gm...> - 2012-12-27 00:38:17
|
Stefan Kuhne wrote the following: > Am 26.12.2012 23:55, schrieb David McCullough: > > Hallo, > > > The -d option selects from OCF drivers. > > > > If you have an OCF driver or a linux driver (that can be used via > > cryptosoft), then you can use if with OCF. > > ah, ok. > I use cryptosoft with geode-aes. That should still be fairly fast I think. > > I haven't seen any mention of using the crypto in a WLAN card. > > Depending on how the API looks for this device it just might not be > > possible, > > It was a idea but it seems, that SMB has 2,5MByte/s in all configs. Yeah, the geode doesn't do anything but aes/sha IIRC, Cheers, Davidm -- David McCullough, da...@sp..., Ph: 0410 560 763 |
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 |
From: Stefan K. <ste...@gm...> - 2012-12-15 02:07:42
Attachments:
signature.asc
|
Hello, I've made some tests with iperf. With openVPN over LAN I get 17Mbit/s with AES-128-CBC and SHA1, with AES-128-CBC and without auth I get 22Mbit/s. My CPU load ist at 100%. What tells /proc/crypto? I get: Guardian 3.9.0-rev24506 # cat /proc/crypto name : cbc(aes) driver : cbc(geode-aes) module : cbc priority : 300 refcnt : 9 selftest : passed type : blkcipher blocksize : 16 min keysize : 16 max keysize : 32 ivsize : 16 geniv : <default> name : cbc(aes) driver : cbc-aes-geode module : kernel priority : 400 refcnt : 9 selftest : passed type : givcipher async : yes blocksize : 16 min keysize : 16 max keysize : 32 ivsize : 16 geniv : chainiv name : ecb(arc4) driver : ecb(arc4-generic) module : ecb priority : 0 refcnt : 1 selftest : passed type : blkcipher blocksize : 1 min keysize : 1 max keysize : 256 ivsize : 0 geniv : <default> name : ecb(arc4) driver : ecb(arc4)-generic module : arc4 priority : 100 refcnt : 1 selftest : passed type : blkcipher blocksize : 1 min keysize : 1 max keysize : 256 ivsize : 0 geniv : <default> name : arc4 driver : arc4-generic module : arc4 priority : 0 refcnt : 3 selftest : passed type : cipher blocksize : 1 min keysize : 1 max keysize : 256 name : cbc(aes) driver : cbc-aes-geode module : geode_aes priority : 400 refcnt : 9 selftest : passed type : blkcipher blocksize : 16 min keysize : 16 max keysize : 32 ivsize : 16 geniv : <default> name : ecb(aes) driver : ecb-aes-geode module : geode_aes priority : 400 refcnt : 1 selftest : passed type : blkcipher blocksize : 16 min keysize : 16 max keysize : 32 ivsize : 0 geniv : <default> name : aes driver : geode-aes module : geode_aes priority : 300 refcnt : 12 selftest : passed type : cipher blocksize : 16 min keysize : 16 max keysize : 32 name : aes driver : aes-asm module : aes_i586 priority : 200 refcnt : 12 selftest : passed type : cipher blocksize : 16 min keysize : 16 max keysize : 32 name : aes driver : aes-generic module : aes_generic priority : 100 refcnt : 1 selftest : passed type : cipher blocksize : 16 min keysize : 16 max keysize : 32 name : stdrng driver : krng module : kernel priority : 200 refcnt : 2 selftest : passed type : rng seedsize : 0 name : md5 driver : md5-generic module : kernel priority : 0 refcnt : 1 selftest : passed type : shash blocksize : 64 digestsize : 16 Guardian 3.9.0-rev24506 # dmesg tells my this with cryptosoft debug: swcr_process() swcr_process_req() crypto OP success 0 swcr_process_req_complete() swcr_process_req_complete crypto_done ccb23e00 Regards, Stefan Kuhne |
From: Stefan K. <ste...@gm...> - 2012-12-15 11:36:48
Attachments:
signature.asc
|
Am 15.12.2012 03:06, schrieb Stefan Kuhne: Hello, > I've made some tests with iperf. > With openVPN over LAN I get 17Mbit/s with AES-128-CBC and SHA1, with > AES-128-CBC and without auth I get 22Mbit/s. I've forgot something. Without ocf I get 15Mbit/s. Regards, Stefan Kuhne |
From: David M. <dav...@mc...> - 2012-12-15 13:55:14
|
Jivin Stefan Kuhne lays it down ... > Am 15.12.2012 03:06, schrieb Stefan Kuhne: > > Hello, > > > I've made some tests with iperf. > > With openVPN over LAN I get 17Mbit/s with AES-128-CBC and SHA1, with > > AES-128-CBC and without auth I get 22Mbit/s. > > I've forgot something. > Without ocf I get 15Mbit/s. Whats the difference in CPU usage ? Not sure why you cannot get 100% CPU though, Cheers, Davidm -- David McCullough, dav...@mc..., Ph:+61 734352815 McAfee - SnapGear http://www.mcafee.com http://www.uCdot.org |
From: Stefan K. <ste...@gm...> - 2012-12-15 14:07:08
Attachments:
signature.asc
|
Am 15.12.2012 14:54, schrieb David McCullough: Hallo, > Whats the difference in CPU usage ? Not sure why you cannot get 100% CPU > though, > it is at 100% total. When I use ocf I've round about 20% usage of ocf_0. An example with another tunnel: 5243 1 root R 2760 1.1 0 59.7 openvpn --config /etc/openvpn/WebSpace.conf --daemon openvpn-WebSpace --management-hold 622 2 root SW 0 0.0 0 3.9 [ocf_0] There I get 1,5MByte/s, but I don't how how fast is the other site. I don't know if I told it. It's a board like Alix with AMD Geode CPU. Regards, Stefan Kuhne |