Thread: [Ocf-linux-users] cryptodev using "native" crypto driver
Brought to you by:
david-m
Menu
▾
▴
ocf-linux-users
|
From: Xianghua X. <x....@fr...> - 2009-04-16 20:41:07
|
Hi, I used ocf/cryptodev on talitos driver and it worked well along with openssl. now with the new talitos driver under drivers/crypto I would like to use the same application-friendly /dev/crypto interface for underlying hardware SEC engine. The cryptodev.c from ocf-linux is dependent on ocf framework. what's needed to get cryptodev working with new security drivers (e.g. drivers/crypto/talitos.c) where no ocf is present? thanks for any tips, xianghua |
|
From: David M. <Dav...@se...> - 2009-04-16 23:07:52
|
Jivin Xianghua Xiao lays it down ... > Hi, > I used ocf/cryptodev on talitos driver and it worked well along with > openssl. now with the new talitos driver under drivers/crypto I would > like to use the same application-friendly /dev/crypto interface for > underlying hardware SEC engine. The cryptodev.c from ocf-linux is > dependent on ocf framework. what's needed to get cryptodev working with > new security drivers (e.g. drivers/crypto/talitos.c) where no ocf is > present? Use OCF just like before, but instead of using the ocf talitos driver, just use cryptosoft. cryptosoft whould use the "in-kernel" drivers to do it's crypto. It's not ideal, but if you are using it just for SSL, there will be little to no penality, Cheers, Davidm -- David McCullough, dav...@se..., Ph:+61 734352815 McAfee - SnapGear http://www.snapgear.com http://www.uCdot.org |
|
From: xianghua x. <x....@fr...> - 2009-04-17 02:17:09
|
David, what do you mean by "in-kernel" driver here? Thanks! xianghua David McCullough wrote: > Jivin Xianghua Xiao lays it down ... > >> Hi, >> I used ocf/cryptodev on talitos driver and it worked well along with >> openssl. now with the new talitos driver under drivers/crypto I would >> like to use the same application-friendly /dev/crypto interface for >> underlying hardware SEC engine. The cryptodev.c from ocf-linux is >> dependent on ocf framework. what's needed to get cryptodev working with >> new security drivers (e.g. drivers/crypto/talitos.c) where no ocf is >> present? >> > > Use OCF just like before, but instead of using the ocf talitos driver, > just use cryptosoft. cryptosoft whould use the "in-kernel" drivers to > do it's crypto. > > It's not ideal, but if you are using it just for SSL, there will be > little to no penality, > > Cheers, > Davidm > > |
|
From: David M. <Dav...@se...> - 2009-04-17 03:25:00
|
Jivin xianghua xiao lays it down ... > David, > > what do you mean by "in-kernel" driver here? The talitos driver that is part of the recent mainline kernels (ie., it is not provided by OCF). Cheers, Davidm > David McCullough wrote: > > Jivin Xianghua Xiao lays it down ... > > > >> Hi, > >> I used ocf/cryptodev on talitos driver and it worked well along with > >> openssl. now with the new talitos driver under drivers/crypto I would > >> like to use the same application-friendly /dev/crypto interface for > >> underlying hardware SEC engine. The cryptodev.c from ocf-linux is > >> dependent on ocf framework. what's needed to get cryptodev working with > >> new security drivers (e.g. drivers/crypto/talitos.c) where no ocf is > >> present? > >> > > > > Use OCF just like before, but instead of using the ocf talitos driver, > > just use cryptosoft. cryptosoft whould use the "in-kernel" drivers to > > do it's crypto. > > > > It's not ideal, but if you are using it just for SSL, there will be > > little to no penality, > > > > Cheers, > > Davidm > > > > > > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > Ocf-linux-users mailing list > Ocf...@li... > https://lists.sourceforge.net/lists/listinfo/ocf-linux-users > -- David McCullough, dav...@se..., Ph:+61 734352815 McAfee - SnapGear http://www.snapgear.com http://www.uCdot.org |
|
From: xianghua x. <x....@fr...> - 2009-04-17 03:29:52
|
thanks a lot! will give it a try on 2.6.28. xianghua David McCullough wrote: > Jivin xianghua xiao lays it down ... > >> David, >> >> what do you mean by "in-kernel" driver here? >> > > The talitos driver that is part of the recent mainline kernels (ie., it > is not provided by OCF). > > Cheers, > Davidm > > >> David McCullough wrote: >> >>> Jivin Xianghua Xiao lays it down ... >>> >>> >>>> Hi, >>>> I used ocf/cryptodev on talitos driver and it worked well along with >>>> openssl. now with the new talitos driver under drivers/crypto I would >>>> like to use the same application-friendly /dev/crypto interface for >>>> underlying hardware SEC engine. The cryptodev.c from ocf-linux is >>>> dependent on ocf framework. what's needed to get cryptodev working with >>>> new security drivers (e.g. drivers/crypto/talitos.c) where no ocf is >>>> present? >>>> >>>> >>> Use OCF just like before, but instead of using the ocf talitos driver, >>> just use cryptosoft. cryptosoft whould use the "in-kernel" drivers to >>> do it's crypto. >>> >>> It's not ideal, but if you are using it just for SSL, there will be >>> little to no penality, >>> >>> Cheers, >>> Davidm >>> >>> >>> >> ------------------------------------------------------------------------------ >> Stay on top of everything new and different, both inside and >> around Java (TM) technology - register by April 22, and save >> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >> 300 plus technical and hands-on sessions. Register today. >> Use priority code J9JMT32. http://p.sf.net/sfu/p >> _______________________________________________ >> Ocf-linux-users mailing list >> Ocf...@li... >> https://lists.sourceforge.net/lists/listinfo/ocf-linux-users >> >> > > |
|
From: Xianghua X. <x....@fr...> - 2009-04-20 19:29:56
|
Here is what I tried, patched ocf-linux to 2.6.28, insmod all modules,
run patched openssl 0.9.8i, openssl "completes" all steps in 0 seconds,
something must be wrong. the in-kernel driver is not even invoked by
looking at interrupts, any idea? Note: i tried ocf/openswan/KLIPS on an
older kernel and openssl worked there, the in-kernel new driver worked
when using setkep to set up ipsec, looks like something is wrong with
the cryptodev stuff:
------------------------------------------
~/ocf # rmmod cryptodev
~/ocf # rmmod cryptosoft
~/ocf # rmmod ocf
~/ocf # lsmod
Module Size Used by
~/ocf # uname -a
Linux mpc8572ds 2.6.28.1-00298-g3cf38ee-dirty #1 SMP Mon Apr 20 10:45:24
CDT 2009 ppc GNU/
Linux
~/ocf # insmod ./ocf.ko
~/ocf # insmod ./cryptodev.ko
~/ocf # insmod ./cryptosoft.ko
~/ocf # insmod ./talitos.ko
talitos ffe30000.crypto: hwrng
alg: No test for authenc(hmac(sha1),cbc(aes))
(authenc-hmac-sha1-cbc-aes-talitos)
talitos ffe30000.crypto: authenc-hmac-sha1-cbc-aes-talitos
alg: No test for authenc(hmac(sha1),cbc(des3_ede))
(authenc-hmac-sha1-cbc-3des-talitos)
talitos ffe30000.crypto: authenc-hmac-sha1-cbc-3des-talitos
alg: No test for authenc(hmac(sha256),cbc(aes))
(authenc-hmac-sha256-cbc-aes-talitos)
talitos ffe30000.crypto: authenc-hmac-sha256-cbc-aes-talitos
alg: No test for authenc(hmac(sha256),cbc(des3_ede))
(authenc-hmac-sha256-cbc-3des-talitos
)
talitos ffe30000.crypto: authenc-hmac-sha256-cbc-3des-talitos
alg: No test for authenc(hmac(md5),cbc(aes))
(authenc-hmac-md5-cbc-aes-talitos)
talitos ffe30000.crypto: authenc-hmac-md5-cbc-aes-talitos
alg: No test for authenc(hmac(md5),cbc(des3_ede))
(authenc-hmac-md5-cbc-3des-talitos)
talitos ffe30000.crypto: authenc-hmac-md5-cbc-3des-talitos
~/ocf # lsmod
Module Size Used by
talitos 18624 0
cryptosoft 11440 0
cryptodev 14500 0
ocf 27484 2 cryptosoft,cryptodev
~/ocf # openssl speed -elapsed -evp des-ede3-cbc -engine cryptodev -cpu
WARNING: can't open config file: /usr/ssl/openssl.cnf
engine "cryptodev" set.
You have chosen to measure elapsed time instead of user CPU time.
To get the most accurate results, try to run this
program when this computer is idle.
Doing des-ede3-cbc for 3s on 16 size blocks: 216688 des-ede3-cbc's in 0.00s
Doing des-ede3-cbc for 3s on 64 size blocks: 128415 des-ede3-cbc's in 0.00s
Doing des-ede3-cbc for 3s on 256 size blocks: 48908 des-ede3-cbc's in 0.00s
Doing des-ede3-cbc for 3s on 1024 size blocks: 14127 des-ede3-cbc's in 0.00s
Doing des-ede3-cbc for 3s on 2048 size blocks: 7230 des-ede3-cbc's in
2147483647.0s
OpenSSL 0.9.8i 15 Sep 2008
built on: Mon Apr 20 12:55:19 CDT 2009
options:bn(64,32) md2(int) rc4(ptr,char) des(idx,risc1,16,long)
aes(partial) idea(int) blo
wfish(idx)
compiler: gcc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_
H -DHAVE_CRYPTODEV -DB_ENDIAN -DB_ENDIAN -DTERMIO -O3 -Wall
available timing options: TIMES TIMEB HZ=7.41098e-322 [sysconf value]
timing function used: ftime
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes /cpu 64 bytes /cpu 256 bytes /cpu
1024 bytes /cpu 204
8 bytes /cpu
des-ede3-cbc
9808352818197981992795330994664242746378032095412947614020858417323457159992
220728377548646966672572860197718924960528369593685784879304276592844431701294994185470557
5506159429746688.00k/%100 0.00k/%100 -0.00k/%100
0.00k/%100 0.0
0k/%100
~/ocf # openssl speed -elapsed -evp des-ede3-cbc -cpu
WARNING: can't open config file: /usr/ssl/openssl.cnf
You have chosen to measure elapsed time instead of user CPU time.
To get the most accurate results, try to run this
program when this computer is idle.
Doing des-ede3-cbc for 3s on 16 size blocks: 217871 des-ede3-cbc's in 0.00s
Doing des-ede3-cbc for 3s on 64 size blocks: 128680 des-ede3-cbc's in 0.00s
Doing des-ede3-cbc for 3s on 256 size blocks: 48925 des-ede3-cbc's in 0.00s
Doing des-ede3-cbc for 3s on 1024 size blocks: 14103 des-ede3-cbc's in
2147483647.0s
Doing des-ede3-cbc for 3s on 2048 size blocks: 7234 des-ede3-cbc's in 0.00s
OpenSSL 0.9.8i 15 Sep 2008
built on: Mon Apr 20 12:55:19 CDT 2009
options:bn(64,32) md2(int) rc4(ptr,char) des(idx,risc1,16,long)
aes(partial) idea(int) blo
wfish(idx)
compiler: gcc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_
H -DHAVE_CRYPTODEV -DB_ENDIAN -DB_ENDIAN -DTERMIO -O3 -Wall
available timing options: TIMES TIMEB HZ=7.41098e-322 [sysconf value]
timing function used: ftime
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes /cpu 64 bytes /cpu 256 bytes /cpu
1024 bytes /cpu 204
8 bytes /cpu
des-ede3-cbc 0.00k/%100 -0.00k/%100
-228998953029974311841503602121312208883
817686549574999287274100565424139180729943013547327548632681026770471405511989488440428768
058454816536123474759035841336940483362802472291300266042584629938696157429255554607213800
12589056.00k/%100
3044265661076964743504699236572542454648112292278445226047045632.00k/%10
0 0.00k/%100
~/ocf # cat /proc/interrupts
CPU0
14: 0 i8259 Level pata_ali
17: 6 OpenPIC Level phy_interrupt, phy_interrupt
18: 652 FSL-MSI Edge ahci
28: 0 OpenPIC Level ehci_hcd:usb1
29: 16 OpenPIC Level eth0_tx
30: 4816 OpenPIC Level eth0_rx
34: 0 OpenPIC Level eth0_er
35: 0 OpenPIC Level eth1_tx
36: 0 OpenPIC Level eth1_rx
40: 0 OpenPIC Level eth1_er
42: 6874 OpenPIC Level serial
43: 0 OpenPIC Level i2c-mpc, i2c-mpc
45: 0 OpenPIC Level talitos
59: 2 OpenPIC Level fsl_espi
251: 0 OpenPIC Edge ipi call function
252: 0 OpenPIC Edge ipi reschedule
253: 0 OpenPIC Edge ipi call function single
BAD: 0
~/ocf #
thanks,
xianghua
xianghua xiao wrote:
> thanks a lot! will give it a try on 2.6.28.
> xianghua
>
> David McCullough wrote:
>
>> Jivin xianghua xiao lays it down ...
>>
>>
>>> David,
>>>
>>> what do you mean by "in-kernel" driver here?
>>>
>>>
>> The talitos driver that is part of the recent mainline kernels (ie., it
>> is not provided by OCF).
>>
>> Cheers,
>> Davidm
>>
>>
>>
>>> David McCullough wrote:
>>>
>>>
>>>> Jivin Xianghua Xiao lays it down ...
>>>>
>>>>
>>>>
>>>>> Hi,
>>>>> I used ocf/cryptodev on talitos driver and it worked well along with
>>>>> openssl. now with the new talitos driver under drivers/crypto I would
>>>>> like to use the same application-friendly /dev/crypto interface for
>>>>> underlying hardware SEC engine. The cryptodev.c from ocf-linux is
>>>>> dependent on ocf framework. what's needed to get cryptodev working with
>>>>> new security drivers (e.g. drivers/crypto/talitos.c) where no ocf is
>>>>> present?
>>>>>
>>>>>
>>>>>
>>>> Use OCF just like before, but instead of using the ocf talitos driver,
>>>> just use cryptosoft. cryptosoft whould use the "in-kernel" drivers to
>>>> do it's crypto.
>>>>
>>>> It's not ideal, but if you are using it just for SSL, there will be
>>>> little to no penality,
>>>>
>>>> Cheers,
>>>> Davidm
>>>>
>>>>
>>>>
>>>>
>>> ------------------------------------------------------------------------------
>>> Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save
>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> Ocf-linux-users mailing list
>>> Ocf...@li...
>>> https://lists.sourceforge.net/lists/listinfo/ocf-linux-users
>>>
>>>
>>>
>>
>>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Ocf-linux-users mailing list
> Ocf...@li...
> https://lists.sourceforge.net/lists/listinfo/ocf-linux-users
>
|
|
From: Kim P. <kim...@fr...> - 2009-04-20 20:17:59
|
On Mon, 20 Apr 2009 14:29:21 -0500 Xianghua Xiao <x....@fr...> wrote: > Here is what I tried, patched ocf-linux to 2.6.28, insmod all modules, > run patched openssl 0.9.8i, openssl "completes" all steps in 0 seconds, > something must be wrong. the in-kernel driver is not even invoked by > looking at interrupts, any idea? Note: i tried ocf/openswan/KLIPS on an try what's sitting in Herbert's cryptodev tree on git.kernel.org instead - that driver has support for cbc-mode aes and 3des (which is what you are testing here). also, please don't top-post/full quote. Thanks, Kim |
|
From: Xianghua X. <x....@fr...> - 2009-04-20 22:11:23
|
compared talitos.c from herbert's git snapshot (2.6.30-rc2) with the
talitos.c I'm using, they're identical. talitos.h does have some
difference, but nothing critical.
i ran "openssl speed -elapsed -cpu -engine cryptodev" which tries all
crypto algorithms, still I got all zeros cpu times. the talitos.ko also
gives zero interrupts. again, setkey-based ipsec works well with the
same talitos driver.
------------------------------------
~/ocf # openssl speed -elapsed -cpu -cpu -engine cryptodev
WARNING: can't open config file: /usr/ssl/openssl.cnf
engine "cryptodev" set.
You have chosen to measure elapsed time instead of user CPU time.
To get the most accurate results, try to run this
program when this computer is idle.
Doing md2 for 3s on 16 size blocks: 99724 md2's in 0.00s
Doing md2 for 3s on 64 size blocks: 51982 md2's in 2147483647.0s
Doing md2 for 3s on 256 size blocks: 17851 md2's in 0.00s
Doing md2 for 3s on 1024 size blocks: 4923 md2's in 0.00s
Doing md2 for 3s on 2048 size blocks: 2504 md2's in 0.00s
Doing md4 for 3s on 16 size blocks: 1137021 md4's in 0.00s
Doing md4 for 3s on 64 size blocks: 965787 md4's in 0.00s
Doing md4 for 3s on 256 size blocks: 706284 md4's in 0.00s
Doing md4 for 3s on 1024 size blocks: 343961 md4's in 0.00s
Doing md4 for 3s on 2048 size blocks: 204119 md4's in 0.00s
Doing md5 for 3s on 16 size blocks: 967079 md5's in 0.00s
Doing md5 for 3s on 64 size blocks: 797822 md5's in 0.00s
Doing md5 for 3s on 256 size blocks: 552616 md5's in 0.00s
Doing md5 for 3s on 1024 size blocks: 249308 md5's in 0.00s
Doing md5 for 3s on 2048 size blocks: 143944 md5's in 0.00s
Doing hmac(md5) for 3s on 16 size blocks: 1136409 hmac(md5)'s in 0.00s
Doing hmac(md5) for 3s on 64 size blocks: 912028 hmac(md5)'s in 0.00s
Doing hmac(md5) for 3s on 256 size blocks: 606583 hmac(md5)'s in 0.00s
Doing hmac(md5) for 3s on 1024 size blocks: 259588 hmac(md5)'s in 0.00s
Doing hmac(md5) for 3s on 2048 size blocks: 147346 hmac(md5)'s in 0.00s
Doing sha1 for 3s on 16 size blocks: 979827 sha1's in 0.00s
Doing sha1 for 3s on 64 size blocks: 784609 sha1's in 2147483647.0s
Doing sha1 for 3s on 256 size blocks: 497955 sha1's in 0.00s
Doing sha1 for 3s on 1024 size blocks: 203198 sha1's in 0.00s
Doing sha1 for 3s on 2048 size blocks: 113558 sha1's in 0.00s
Doing sha256 for 3s on 16 size blocks: 817807 sha256's in 0.00s
Doing sha256 for 3s on 64 size blocks: 494637 sha256's in 0.00s
Doing sha256 for 3s on 256 size blocks: 230091 sha256's in 0.00s
Doing sha256 for 3s on 1024 size blocks: 73428 sha256's in 0.00s
Doing sha256 for 3s on 2048 size blocks: 38488 sha256's in 0.00s
Doing sha512 for 3s on 16 size blocks: 181366 sha512's in 0.00s
Doing sha512 for 3s on 64 size blocks: 180995 sha512's in 0.00s
Doing sha512 for 3s on 256 size blocks: 66900 sha512's in 0.00s
Doing sha512 for 3s on 1024 size blocks: 23449 sha512's in 0.00s
Doing sha512 for 3s on 2048 size blocks: 12567 sha512's in 0.00s
Doing rmd160 for 3s on 16 size blocks: 814302 rmd160's in 0.00s
Doing rmd160 for 3s on 64 size blocks: 602075 rmd160's in 0.00s
Doing rmd160 for 3s on 256 size blocks: 338620 rmd160's in 0.00s
Doing rmd160 for 3s on 1024 size blocks: 123634 rmd160's in 0.00s
Doing rmd160 for 3s on 2048 size blocks: 66941 rmd160's in 0.00s
Doing rc4 for 3s on 16 size blocks: 10996110 rc4's in 0.00s
Doing rc4 for 3s on 64 size blocks: 3256984 rc4's in 0.00s
Doing rc4 for 3s on 256 size blocks: 853415 rc4's in 0.00s
Doing rc4 for 3s on 1024 size blocks: 215958 rc4's in 0.00s
Doing rc4 for 3s on 2048 size blocks: 108198 rc4's in 0.00s
Doing des cbc for 3s on 16 size blocks: 2223476 des cbc's in 0.00s
Doing des cbc for 3s on 64 size blocks: 592607 des cbc's in 0.00s
Doing des cbc for 3s on 256 size blocks: 150612 des cbc's in 0.00s
Doing des cbc for 3s on 1024 size blocks: 37810 des cbc's in 0.00s
Doing des cbc for 3s on 2048 size blocks: 18919 des cbc's in 0.00s
Doing des ede3 for 3s on 16 size blocks: 842233 des ede3's in 0.00s
Doing des ede3 for 3s on 64 size blocks: 216120 des ede3's in 0.00s
Doing des ede3 for 3s on 256 size blocks: 54372 des ede3's in 0.00s
Doing des ede3 for 3s on 1024 size blocks: 13615 des ede3's in 0.00s
Doing des ede3 for 3s on 2048 size blocks: 6809 des ede3's in 0.00s
Doing aes-128 cbc for 3s on 16 size blocks: INFO: task migration/1:6
blocked for more than
120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
migration/1 D 00000000 0 6 2
Call Trace:
[ef845e70] [deadbeef] 0xdeadbeef (unreliable)
[ef845f30] [c0007928] __switch_to+0x8c/0xdc
[ef845f50] [c03c94cc] schedule+0x214/0x5f0
[ef845fd0] [c00545cc] kthread+0x30/0x84
[ef845ff0] [c000ef24] kernel_thread+0x4c/0x68
INFO: task ksoftirqd/1:7 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
ksoftirqd/1 D 00000000 0 7 2
Call Trace:
[ef849e70] [deadbeef] 0xdeadbeef (unreliable)
[ef849f30] [c0007928] __switch_to+0x8c/0xdc
[ef849f50] [c03c94cc] schedule+0x214/0x5f0
[ef849fd0] [c00545cc] kthread+0x30/0x84
[ef849ff0] [c000ef24] kernel_thread+0x4c/0x68
INFO: task watchdog/1:8 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
watchdog/1 D 00000000 0 8 2
Call Trace:
[ef84be70] [deadbeef] 0xdeadbeef (unreliable)
[ef84bf30] [c0007928] __switch_to+0x8c/0xdc
[ef84bf50] [c03c94cc] schedule+0x214/0x5f0
[ef84bfd0] [c00545cc] kthread+0x30/0x84
[ef84bff0] [c000ef24] kernel_thread+0x4c/0x68
4043240 aes-128 cbc's in 0.00s
Doing aes-128 cbc for 3s on 64 size blocks: 1151532 aes-128 cbc's in 0.00s
Doing aes-128 cbc for 3s on 256 size blocks: 295851 aes-128 cbc's in 0.00s
Doing aes-128 cbc for 3s on 1024 size blocks: 74493 aes-128 cbc's in 0.00s
Doing aes-128 cbc for 3s on 2048 size blocks: 37265 aes-128 cbc's in 0.00s
Doing aes-192 cbc for 3s on 16 size blocks: 3758279 aes-192 cbc's in 0.00s
Doing aes-192 cbc for 3s on 64 size blocks: 1020032 aes-192 cbc's in 0.00s
Doing aes-192 cbc for 3s on 256 size blocks: 261262 aes-192 cbc's in
2147483647.0s
Doing aes-192 cbc for 3s on 1024 size blocks: 65722 aes-192 cbc's in 0.00s
Doing aes-192 cbc for 3s on 2048 size blocks: 32873 aes-192 cbc's in
2147483647.0s
Doing aes-256 cbc for 3s on 16 size blocks: 3400667 aes-256 cbc's in 0.00s
Doing aes-256 cbc for 3s on 64 size blocks: 915476 aes-256 cbc's in 0.00s
Doing aes-256 cbc for 3s on 256 size blocks: 233892 aes-256 cbc's in 0.00s
Doing aes-256 cbc for 3s on 1024 size blocks: 58799 aes-256 cbc's in 0.00s
Doing aes-256 cbc for 3s on 2048 size blocks: 29412 aes-256 cbc's in 0.00s
Doing aes-128 ige for 3s on 16 size blocks: 3873740 aes-128 ige's in 0.00s
Doing aes-128 ige for 3s on 64 size blocks: 1137303 aes-128 ige's in 0.00s
Doing aes-128 ige for 3s on 256 size blocks: 298027 aes-128 ige's in 0.00s
Doing aes-128 ige for 3s on 1024 size blocks: 75414 aes-128 ige's in 0.00s
Doing aes-128 ige for 3s on 2048 size blocks: 37760 aes-128 ige's in 0.00s
Doing aes-192 ige for 3s on 16 size blocks: 3494993 aes-192 ige's in 0.00s
Doing aes-192 ige for 3s on 64 size blocks: 1008886 aes-192 ige's in 0.00s
Doing aes-192 ige for 3s on 256 size blocks: 262940 aes-192 ige's in 0.00s
Doing aes-192 ige for 3s on 1024 size blocks: 66442 aes-192 ige's in 0.00s
Doing aes-192 ige for 3s on 2048 size blocks:
~/ocf # cat /proc/interrupts
CPU0
14: 0 i8259 Level pata_ali
17: 6 OpenPIC Level phy_interrupt, phy_interrupt
18: 380 FSL-MSI Edge ahci
28: 0 OpenPIC Level ehci_hcd:usb1
29: 10 OpenPIC Level eth0_tx
30: 11143 OpenPIC Level eth0_rx
34: 0 OpenPIC Level eth0_er
35: 0 OpenPIC Level eth1_tx
36: 0 OpenPIC Level eth1_rx
40: 0 OpenPIC Level eth1_er
42: 1727 OpenPIC Level serial
43: 0 OpenPIC Level i2c-mpc, i2c-mpc
45: 0 OpenPIC Level talitos
59: 2 OpenPIC Level fsl_espi
251: 0 OpenPIC Edge ipi call function
252: 0 OpenPIC Edge ipi reschedule
253: 0 OpenPIC Edge ipi call function single
BAD: 0
~/ocf #
thanks,
xianghua
Kim Phillips wrote:
> On Mon, 20 Apr 2009 14:29:21 -0500
> Xianghua Xiao <x....@fr...> wrote:
>
>
>> Here is what I tried, patched ocf-linux to 2.6.28, insmod all modules,
>> run patched openssl 0.9.8i, openssl "completes" all steps in 0 seconds,
>> something must be wrong. the in-kernel driver is not even invoked by
>> looking at interrupts, any idea? Note: i tried ocf/openswan/KLIPS on an
>>
>
> try what's sitting in Herbert's cryptodev tree on git.kernel.org
> instead - that driver has support for cbc-mode aes and 3des (which is
> what you are testing here).
>
> also, please don't top-post/full quote.
>
> Thanks,
>
> Kim
>
|
|
From: Kim P. <kim...@fr...> - 2009-04-20 22:32:03
|
On Mon, 20 Apr 2009 17:10:52 -0500 Xianghua Xiao <x....@fr...> wrote: > compared talitos.c from herbert's git snapshot (2.6.30-rc2) with the > talitos.c I'm using, they're identical. talitos.h does have some > difference, but nothing critical. are you sure you're using the right tree? $ git diff --stat v2.6.28 -- drivers/crypto/talitos.c drivers/crypto/talitos.c | 786 +++++++++++++++++++++++++++++++++------------- 1 files changed, 575 insertions(+), 211 deletions(-) Kim |
|
From: Kim P. <kim...@fr...> - 2009-04-22 00:12:54
|
On Tue, 21 Apr 2009 09:04:46 -0500 Xianghua Xiao <x....@fr...> wrote: > the 2.6.28 kernel/BSP I used does have the newest talitos.c, the same as > 2.6.30-rc2 from herbert's git tree. I can't tell which of Herbert's trees you're talking about. If /proc/crypto contains cbc-3des-talitos and cbc-aes-talitos entries, and cryptosoft is loaded, and you're getting the same performance as when no talitos h/w driver is loaded, then it sounds like you've found a bug. Kim |
|
From: David M. <Dav...@se...> - 2009-04-22 01:22:53
|
Jivin Kim Phillips lays it down ... > On Tue, 21 Apr 2009 09:04:46 -0500 > Xianghua Xiao <x....@fr...> wrote: > > > the 2.6.28 kernel/BSP I used does have the newest talitos.c, the same as > > 2.6.30-rc2 from herbert's git tree. > > I can't tell which of Herbert's trees you're talking about. > > If /proc/crypto contains cbc-3des-talitos and cbc-aes-talitos entries, > and cryptosoft is loaded, and you're getting the same performance as > when no talitos h/w driver is loaded, then it sounds like you've found > a bug. Yep, and it's possible that cryptosoft needs a patch to handle async crypto drivers. I think I have one in my inbox or perhaps it was posted to the list. Let me know if your talitos support is good and I'll go digging for the cryptosoft changes you will need, Cheers, Davidm -- David McCullough, dav...@se..., Ph:+61 734352815 McAfee - SnapGear http://www.snapgear.com http://www.uCdot.org |
|
From: Xianghua X. <x....@fr...> - 2009-04-21 14:05:37
|
the 2.6.28 kernel/BSP I used does have the newest talitos.c, the same as 2.6.30-rc2 from herbert's git tree. thanks, xianghua Kim Phillips wrote: > On Mon, 20 Apr 2009 17:10:52 -0500 > Xianghua Xiao <x....@fr...> wrote: > > >> compared talitos.c from herbert's git snapshot (2.6.30-rc2) with the >> talitos.c I'm using, they're identical. talitos.h does have some >> difference, but nothing critical. >> > > are you sure you're using the right tree? > > $ git diff --stat v2.6.28 -- drivers/crypto/talitos.c > drivers/crypto/talitos.c | 786 +++++++++++++++++++++++++++++++++------------- > 1 files changed, 575 insertions(+), 211 deletions(-) > > Kim > |
Thanks for helping keep SourceForge clean.
X