Date: Wed, 19 Jul 2006 16:38:17 +0200 (CEST) From: Michael Reifenberger <mike@Reifenberger.com> To: freebsd-hackers@freebsd.org, ato@iem.pw.edu.pl Subject: Re: VIA padlock performance Message-ID: <20060719163232.C38044@fw.reifenberger.com> In-Reply-To: <200607191414.k6JEE4Dw050307@lurza.secnetix.de> References: <200607191414.k6JEE4Dw050307@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Jul 2006, Oliver Fromme wrote:
...
> You will also need "cryptodev" in addition to "crypto".
> "crypto" manages only in-kernel access to the cryptographic
> facilities (including hardware acceleration through the
> padlock driver), which is used by FAST_IPSEC, for example.
> "cryptodev" will enable access by userland applications
> (e.g. scp) and libraries (OpenSSL) through /dev/crypto.
>
With OpenSSL you have two choices:
engine cryptodev : uses /dev/crypto
engine padlock : uses the xcrypt commands directly
engine padlock should be the fastest of course.
Bye/2
---
Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting
Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com
http://www.plaut.de | http://www.Reifenberger.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060719163232.C38044>