Synopsis: [crypto] [patch] AES-192 and AES-256 support for HW-accellerators ie. 
Hifn 795x /  and OpenSSL engine 0.9.8e to _default_ use Cryptodev

State-Changed-From-To: open->feedback
State-Changed-By: jmg
State-Changed-When: Fri Jan 24 21:35:22 UTC 2014
State-Changed-Why: 
Is this patch still applicable?  I recently tried aes modes w/ OpenSSL
(we've updated to 1.0.1 in 10-R and HEAD) and it will default to using
cryptodev over the internal AES-NI implementation if cryptodev module
is loaded...

Also, you cannot just use openssl speed aes to test, as it will not use
the normal path..  you have to use the -evp flag to force it to go through
the normal device selection path...  When using the -evp flag you should
see very short CPU times, like:
Doing aes-128-cbc for 3s on 16 size blocks: 910409 aes-128-cbc's in 0.26s

instead of 3.00s as that is a measure of CPU time not real time, and w/
an accelerator, the accelerator is doing the work, not the local process...

http://www.freebsd.org/cgi/query-pr.cgi?pr=120270
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to