Subject: gxlsb(4) on NetBSD-4-i386 w/ arinfotek 3011
To: None <,,>
From: Brian A. Seklecki <>
List: tech-crypto
Date: 09/17/2007 20:31:48
Hi all!

First off, thanks to everyone who contributed to this driver!

Secondly, here are the dmesg(8) excerpts from a 09/14/07 build:

NetBSD 4.0_RC1 (CFRDMDROOT.MPACPI-$Revision: $) #1: Mon Sep 17 
19:26:45 EDT 2007
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Geode LX (586-class), 499.92 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

npx1 at pnpbios0 index 5 (PNP0C04)
npx1: io f0-ff, irq 13
npx1: reported by CPUID; using exception 16

glxsb0 at pci0 dev 1 function 2: RNG AES

# openssl version
OpenSSL 0.9.8e 23 Feb 2007

Here is the physical device:

I'm going to do some benchmark comparisons on the unit.  I will forward 
results around.  Both "openssl speed" and generic disk-I/O (newfs, etc.) 
on cgd(4). I'm hoping to take advantage of the AES accelleration to 
improve cgd(4).

Presumably as long as the aes-cbc-{128,192,256} is used, the default 
OpenSSL crypt(4) engine of "cryptodev" will be selected (but I haven't 
tried yet)

More details soon

 	-lava (Brian A. Seklecki - Pittsburgh, PA, USA)

     "Guilty? Yeah. But he knows it. I mean, you're guilty.
     You just don't know it. So who's really in jail?"
     ~Maynard James Keenan