Linux cryptographic layer development
 help / color / mirror / Atom feed
From: David McCullough <david_mccullough@au.securecomputing.com>
To: Tripurari Prasad <tripurari.prasad@gdatech.co.in>
Cc: linux-crypto@vger.kernel.org
Subject: Re: problem using cryptosft
Date: Thu, 7 Dec 2006 21:04:40 +1000	[thread overview]
Message-ID: <20061207110440.GA7448@au.securecomputing.com> (raw)
In-Reply-To: <4574EEC1.6060503@gdatech.co.in>


Jivin Tripurari Prasad lays it down ...
> Hi
> 	I have been trying to use OCF release 0cf-linux-20060331
> for software acceleration in x86 machine.
> As given I have upgraded the openssl to version 0.9.8a and applied the ssl 
> patch
> Also added the ocf as module in kernel and enabled the OCF
> There are No Hardware engine I am using.I intend to use software engine only
> 
> however when i try to run the test using openssl
> i get the errors saying inavalid engine .
> 
> 
> invalid engine "cryptosoft"

cryptosoft is the kernel driver,  cryptodev is the "engine",  though you
do not need to specify it.  If you have cryptodev loaded and a patched
openssl,  it will use the cryptodev engine by default.

Cheers,
Davidm

> 5733:error:25066067:DSO support routines:DLFCN_LOAD:could not load the 
> shared 
> library:dso_dlfcn.c:162:filename(/usr/local/ssl/lib/engines/libcryptosoft.so):
> /usr/local/ssl/lib/engines/libcryptosoft.so: cannot open shared object 
> file: No such file or directory
> 5733:error:25070067:DSO support routines:DSO_load:could not load the 
> shared library:dso_lib.c:244:
> 5733:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
> found:eng_dyn.c:450:
> 5733:error:2606A074:engine routines:ENGINE_by_id:no such 
> engine:eng_list.c:415:id=cryptosoft
> 5733:error:25066067:DSO support routines:DLFCN_LOAD:could not load the 
> shared library:dso_dlfcn.c:162:filename(libcryptosoft.so): 
> libcryptosoft.so: cannot open shared object file: No such file or directory
> 5733:error:25070067:DSO support routines:DSO_load:could not load the  
> shared library:dso_lib.c:244:
> 5733:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
> found:eng_dyn.c:450:
> 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-cbc for 3s on 16 size blocks: 8672638 des-cbc's in 3.00s
> Doing des-cbc for 3s on 64 size blocks: 3367797 des-cbc's in 3.00s
> Doing des-cbc for 3s on 256 size blocks: 872436 des-cbc's in 3.00s
> Doing des-cbc for 3s on 1024 size blocks: 220186 des-cbc's in 3.00s
> Doing des-cbc for 3s on 8192 size blocks: 27519 des-cbc's in 3.00s
> OpenSSL 0.9.8a 11 Oct 2005
> built on: Fri Dec  1 20:40:05 IST 2006
> options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) 
> aes(partial) idea(int) blowfish(idx)
> compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H 
> -mcpu=pentium -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall 
> -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DSHA1_ASM -DMD5_ASM 
> -DRMD160_ASM -DAES_ASM
> available timing options: TIMES TIMEB HZ=100 [sysconf value]
> timing function used: ftime
> The 'numbers' are in 1000s of bytes per second processed.
> type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 
> bytes
> des-cbc          46223.25k    71846.34k    74447.87k    75156.82k    
> 75145.22k
> [root@localhost /]#
> -
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
David McCullough,  david_mccullough@securecomputing.com,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org http://www.cyberguard.com

      reply	other threads:[~2006-12-07 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05  4:00 problem using cryptosft Tripurari Prasad
2006-12-07 11:04 ` David McCullough [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061207110440.GA7448@au.securecomputing.com \
    --to=david_mccullough@au.securecomputing.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=tripurari.prasad@gdatech.co.in \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox