From owner-freebsd-current@FreeBSD.ORG  Sun Mar  7 09:44:24 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from hub.freebsd.org (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP id 9019B106566B;
	Sun,  7 Mar 2010 09:44:23 +0000 (UTC)
	(envelope-from nork@FreeBSD.org)
Date: Sun, 7 Mar 2010 18:44:22 +0900
From: Norikatsu Shigemura <nork@FreeBSD.org>
To: David Ehrmann <ehrmann@gmail.com>, Julian Elischer <julian@elischer.org>
Message-Id: <20100307184422.7007747d.nork@FreeBSD.org>
In-Reply-To: <4B934354.4030002@elischer.org>
References: <4B934015.8000908@gmail.com>
	<4B934354.4030002@elischer.org>
X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.5; i386-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, Norikatsu Shigemura <nork@FreeBSD.org>
Subject: Re: Core i5 AES acceleration
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2010 09:44:24 -0000

Hi Devid and Julian.

On Sat, 06 Mar 2010 22:10:28 -0800
Julian Elischer <julian@elischer.org> wrote:
> David Ehrmann wrote:
> > Does FreeBSD currently support cryptographic acceleration for AES on the 
> > Core i5 CPU?  I searched, but couldn't find anything, and the crypto(4) 
> > manpage only lists these divers in "see also:"
> no, but if you write a driver for it we will... :-)
> (most things in open source happen because someone needs it.)

	I found Linux's code: http://lwn.net/Articles/311094/
	I think that it looks too easy, maybe, we should implement aesni(4)
	like padlock(4).