Date: Mon, 08 Mar 2010 18:10:52 -0600 From: "James R. Van Artsdalen" <james-freebsd-current@jrv.org> To: Norikatsu Shigemura <nork@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, David Ehrmann <ehrmann@gmail.com>, Julian Elischer <julian@elischer.org> Subject: Re: Core i5 AES acceleration Message-ID: <4B95920C.5000909@jrv.org> In-Reply-To: <20100309080951.b1a37510.nork@FreeBSD.org> References: <4B934015.8000908@gmail.com> <4B934354.4030002@elischer.org> <20100307184422.7007747d.nork@FreeBSD.org> <4B93E96B.8090002@gmail.com> <20100309080951.b1a37510.nork@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Norikatsu Shigemura wrote: > According to http://en.wikipedia.org/wiki/AES-NI , we can get > specification document: http://software.intel.com/file/20457 . > > I saw it, and consider that we can release under BSDL. Because > of 'from specification'. That document is short on details, such as the opcodes and machine implementation details (flags, etc). The XMM registers are used. That may be a problem for kernel code. When last I looked openssl did not use /dev/crypt - it's not clear how big the benefit would be from doing this if nothing that uses openssl wins. It might be more beneficial to FreeBSD to patch openssl to use /dev/crypt. If it turns out to not be a significant win then that might hint that the AES opcodes won't be significant win in general either.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B95920C.5000909>