AMD Geode LX crypto accelerator (glxsb)

Patrick Lamaizière patfbsd at
Mon Jun 23 17:48:03 UTC 2008

Le Sun, 22 Jun 2008 21:20:02 +0200,
"Ivan Voras" <ivoras at> a écrit :


> The 'numbers' are in 1000s of bytes per second processed.
> type             16 bytes     64 bytes    256 bytes   1024 bytes
> 8192 bytes aes-128 cbc       5359.57k     5577.49k     5654.53k
> 5639.81k     5679.65k aes-128-cbc        394.62k     1471.97k
> 5457.89k    15097.21k    25895.72k

I've got the same results. The encryption of a file of 360 MBytes takes
around 20s with the hardware and 1m10s by software.

I am playing to overload my box (a soekris net5501) with ping floods on
ipsec (hmac-md5 and rijndael) by a modern computer.

With four 'ping -f -s 3000', 'top' reports 
CPU "0.4% user 0.0 nice 1.6% system, 90.3% interrupt,  7.8% idle".

With five 'ping', top does not run, and the kernel does not
display the message 'limiting icmp ping response to 300 to 200' anymore
too (on the serial console).

With the hardware, i can use 8 flood pings without any problem.
Top shows 
CPU:  0.0% user,  0.0% nice, 33.5% system, 12.5% interrupt, 54.1% idle

And the kernel displays "limiting icmp ping response from 900 to 200
packets/s.", instead '300 to 200'.

So it seems there is a real improvement.


More information about the freebsd-hackers mailing list