Date: Thu, 13 Sep 2018 15:44:13 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Lev Serebryakov <lev@FreeBSD.org>, Kevin Oberman <rkoberman@gmail.com> Cc: current <current@freebsd.org>, brnrd@freebsd.org, Jung-uk Kim <jkim@freebsd.org> Subject: Re: Speed problems with both system openssl and security/openssl-devel Message-ID: <73a0934b-136f-785e-57bc-1f5624eea4fa@FreeBSD.org> In-Reply-To: <7316152.20180913112742@serebryakov.spb.ru> References: <43892083.20180913024646@serebryakov.spb.ru> <CAN6yY1usNXCzpnLhHLqbhcjHr6Y4X0%2BTrXiJzNAFY81S5nbzHw@mail.gmail.com> <7316152.20180913112742@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/13/18 1:27 AM, Lev Serebryakov wrote: > Hello Kevin, > > Thursday, September 13, 2018, 6:32:30 AM, you wrote: > > >> This is probably not the issue, but aesni is not in the GENERIC kernel. Are you sure aesni.ko is loaded? >> % kldstat | grep aesni > I'm not using modules, as it is NanoBSD image build for minimal size ant > maximal efficiency. But I have aesni in my kernel config for sure: > > % grep aesni ~/nanobsd/gatevay.v3/J3160 > device aesni >From my understanding of the OpenSSL code, it doesn't use the kernel driver at all (the kernel driver is only needed for in-kernel crypto such as IPSec or GELI). AESNI are just instructions that can be used in userland, and OpenSSL's AESNI acceleration is purely different routines in userland. I would verify if AESNI shows up in the CPU features in dmesg first (if it doesn't I'd check for a BIOS option disabling it). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?73a0934b-136f-785e-57bc-1f5624eea4fa>