From owner-freebsd-stable@FreeBSD.ORG Fri Nov 12 21:29:14 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80D7A106567A for ; Fri, 12 Nov 2010 21:29:14 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 387618FC13 for ; Fri, 12 Nov 2010 21:29:14 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:808a:bf97:8eb:f23b] ([IPv6:2607:f3e0:0:4:808a:bf97:8eb:f23b]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oACLT2Fw065089 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 12 Nov 2010 16:29:02 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4CDDB182.4060707@sentex.net> Date: Fri, 12 Nov 2010 16:28:34 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Kostik Belousov References: <4CDD562D.3050403@isletech.net> <20101112202603.GD2392@deviant.kiev.zoral.com.ua> In-Reply-To: <20101112202603.GD2392@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: Daryl Richards , freebsd-stable@freebsd.org Subject: Re: AESNI X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2010 21:29:14 -0000 On 11/12/2010 3:26 PM, Kostik Belousov wrote: > On Fri, Nov 12, 2010 at 09:58:53AM -0500, Daryl Richards wrote: >> I'm wondering what the status is of AES-NI in 8-STABLE? I can find >> references to it being put into 9 back in July, with the note that it >> would be MFC'ed within a month, but as far as I've been able to find, >> nothing after that. > As a public service, since I already got several private mails, > I will state the current situation: > > AESNI merge depends on the merge of r208833 and a lot of followups to > r208833. The merge of r208833 needs r208453, that was committed to stable/8 > only recently, since it required an approval from re@. > > This delay together with lack of the time recently on my side makes me > skeptical about chances to have aesni(4) in 8.2. > > Please note that aesni(4) is not needed to use AESNI in usermode. BTW, has anyone tried merging the patch at http://rt.openssl.org/Ticket/Display.html?id=2067&user=guest&pass=guest to RELENG_8's openssl ? ---Mike