Date: Fri, 7 Dec 2018 09:43:21 -0800 From: John Baldwin <jhb@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com>, John Nielsen <lists@jnielsen.net> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: /dev/crypto not being used in 12-STABLE Message-ID: <ade442a5-92d0-11e6-5720-05345566ee1a@FreeBSD.org> In-Reply-To: <20181207001933.GH52540@kib.kiev.ua> References: <A418F9A1-7298-4DA7-A185-BD16941BEC46@jnielsen.net> <CAGMYy3vKez_NR6rtcFDGVsWV=qs%2BiaoAwb-D0ed0zT5og9RbOA@mail.gmail.com> <F67BC606-6210-48DD-B924-FF90C26704A1@jnielsen.net> <0b3d8b81-4ed2-e900-9f0e-46ac7006a705@FreeBSD.org> <E00380E2-581C-4BB6-96B4-DEF3445ED4D4@jnielsen.net> <20181207001933.GH52540@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/6/18 4:19 PM, Konstantin Belousov wrote: > On Thu, Dec 06, 2018 at 04:48:35PM -0700, John Nielsen wrote: >> Is aesni(4) even required if all you want is userland acceleration? >> > No, it is not. Same for rdrand_rng(4), if an application uses hw random > source directly. To elaborate further, aesni(4) is only useful to accelerate in-kernel crypto use (e.g. IPSec or GELI). The fact that /dev/crypto trys to use it by default is a bug (IMO) that I'm planning on addressing. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade442a5-92d0-11e6-5720-05345566ee1a>