From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 19 14:38:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62D8116A4DA for ; Wed, 19 Jul 2006 14:38:22 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E489943D49 for ; Wed, 19 Jul 2006 14:38:19 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from mail01.m-online.net (svr21.m-online.net [192.168.3.149]) by mail-out.m-online.net (Postfix) with ESMTP id 44FCF98229; Wed, 19 Jul 2006 16:38:18 +0200 (CEST) Received: from fw.reifenberger.com (ppp-62-245-163-2.dynamic.mnet-online.de [62.245.163.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.m-online.net (Postfix) with ESMTP id 3599691A74; Wed, 19 Jul 2006 16:38:18 +0200 (CEST) Received: from localhost (mike@localhost) by fw.reifenberger.com (8.13.6/8.13.4/Submit) with ESMTP id k6JEcHPD038070; Wed, 19 Jul 2006 16:38:17 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Wed, 19 Jul 2006 16:38:17 +0200 (CEST) From: Michael Reifenberger To: freebsd-hackers@freebsd.org, ato@iem.pw.edu.pl In-Reply-To: <200607191414.k6JEE4Dw050307@lurza.secnetix.de> Message-ID: <20060719163232.C38044@fw.reifenberger.com> References: <200607191414.k6JEE4Dw050307@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: VIA padlock performance X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 14:38:22 -0000 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