Re: glxsb(4) doesn't appear to be working for me (was: AMD Geode LX Security Block)
Thor Lancelot Simon <[email protected]> Fri, 30 Oct 2009 16:15:06 -0400
| Newsgroups | gmane.os.netbsd.devel.crypto |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Oct 30, 2009 at 04:12:26PM -0400, Thor Lancelot Simon wrote: > > The workaround is to trick it into thinking it's testing some other > kind of block-oriented algorithm by telling it to look up the cipher > *by its EVP* which forces it to use the EVP layer, so the engine layer > sees the requests. This is what the -evp switch on the command line > accomplishes. The other thing is, using the "cryptodev" engine causes most of the actual work to be done in the kernel. So you need -elapsed on the openssl speed command line or you'll get false, insanely high results because it will track only the amount of time spent in the userspace openssl process. When you use -multi N I think it also forces the use of -elapsed. -- Thor Lancelot Simon [email protected] "Even experienced UNIX users occasionally enter rm *.* at the UNIX prompt only to realize too late that they have removed the wrong segment of the directory structure." - Microsoft WSS whitepaper