From owner-freebsd-current@FreeBSD.ORG Fri Aug 23 19:31:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9983C15C for ; Fri, 23 Aug 2013 19:31:12 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 5D14B2E2B for ; Fri, 23 Aug 2013 19:31:12 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id 31F0C4F1C; Fri, 23 Aug 2013 19:31:11 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 626F62FDF2; Fri, 23 Aug 2013 21:30:34 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Mike Tancsa Subject: Re: patch to improve AES-NI performance References: <20130822202027.GH94127@funkthat.com> <20130823151615.GD41379@roberto02-aw.erc.corp.eurocontrol.int> <52177F0B.9020906@sentex.net> <20130823180513.GM94127@funkthat.com> <5217A7B5.8040904@sentex.net> <20130823185241.GO94127@funkthat.com> Date: Fri, 23 Aug 2013 21:30:33 +0200 In-Reply-To: <20130823185241.GO94127@funkthat.com> (John-Mark Gurney's message of "Fri, 23 Aug 2013 11:52:41 -0700") Message-ID: <86d2p419ye.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Ollivier Robert , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 19:31:12 -0000 John-Mark Gurney writes: > Mike Tancsa writes: > > John-Mark Gurney writes: > > > My patch would only effect userland applications that use /dev/crypto= ... > > For me its ssh which I think does, no ? > It looks like it uses OpenSSL for it's crypto, not /dev/crypto... It uses OpenSSL engines, which use /dev/crypto. This is why we had to turn off sandbox mode - a CRIOGET ioctl fails because the sandbox code sets RLIMIT_NOFILES to 0. (trimming security@ from the cc: list as it's an alias for secteam@ which is not the appropriate venue for this discussion.) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no