Re: glxsb(4) doesn't appear to be working for me (was: AMD Geode LX Security Block)

[Thor Lancelot Simon <tls%panix.com@localhost>]

On Thu, Oct 29, 2009 at 09:20:16PM -0400, Greg A. Woods wrote:
> ["Jared D. McNeill" wrote some time ago:]
> >
> > Ok, thanks to a bunch of helpful hints on and off list, here we go:
> >
> > swcrypto:
> >
> >   aes-128-cbc 3688.28k 4064.06k 4185.64k 4216.48k 4221.59k
> >
> > hwcrypto:
> >
> >   aes-128-cbc 372.70k 1422.76k 5098.58k 13612.23k 26804.31k
> 
> 
> I've got NetBSD-4 running here on a PC Engines ALIX.2d3 board.
> 
> My dmesg shows:
> 
> cpu0: AMD Geode LX (586-class), 498.08 MHz, id 0x5a2
> cpu0: features 88a93d<FPU,DE,PSE,TSC,MSR,CX8,SEP>
> cpu0: features 88a93d<PGE,CMOV,MPC,MMX>
> cpu0: "Geode(TM) Integrated Processor by AMD PCS"
> cpu0: I-cache 64 KB 32B/line 16-way, D-cache 64 KB 32B/line 16-way
> cpu0: L2 cache 128 KB 32B/line 4-way
> cpu0: ITLB 16 4 KB entries fully associative
> cpu0: DTLB 16 4 KB entries fully associative
> cpu0: 8 page colors
> [[....]]
> glxsb0 at pci0 dev 1 function 2: revision 0: RNG AES
> 
> 
> Open SSL seems to say what I'm told I should expect it to say:
> 
>       # openssl version
>       OpenSSL 0.9.8e 23 Feb 2007
> 
>       # openssl engine -c
>       (cryptodev) BSD cryptodev engine

You may need to explicitly specify -engine cryptodev, and note that you
will not get *any* accelleration from openssl speed for any cipher
unless you specify it as an "evp" instead of by the shortcut name:

openssl speed -engine cryptodev -elapsed -evp aes-128-cbc

FWIW, glxsb is not very efficient and the syscall overhead will just
kill you for all but very large requests.  You may see better results
with -multi 32 to get some parallelism going to hide the latency.

Thor