Lev Serebryakov wrote this message on Mon, Sep 17, 2018 at 23:52 +0300:
> Thursday, September 13, 2018, 2:46:46 AM, you wrote:
>
> > Linux have openssl 1.1.0f, and I've tried both system /usr/bin/openssl
> > (1.0.2p)
> > and /usr/local/bin/openssl from security/openssl-devel port (1.1.0i),
>
Hello Lev,
Thursday, September 13, 2018, 2:46:46 AM, you wrote:
> Linux have openssl 1.1.0f, and I've tried both system /usr/bin/openssl
> (1.0.2p)
> and /usr/local/bin/openssl from security/openssl-devel port (1.1.0i), results
> are
> virtually the same. I have "ASM" and "SSE2" options
On 17.09.2018 10:40, Daniel Nebdal wrote:
> Could it be relevant that the Debian binary was probably compiled with
> gcc, and the FreeBSD binary with clang?
Maybe. Now I'm trying to trace codepath of "openssl speed -evp
aes-256-cbc" on FreeBSD to understand where and why it refuses to use
AES.
On Fri, 14 Sep 2018 at 02:12, Lev Serebryakov wrote:
>
> Hello John,
>
> Friday, September 14, 2018, 1:44:13 AM, you wrote:
>
> >> % 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
Hello John,
Friday, September 14, 2018, 1:44:13 AM, you wrote:
>> % 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).
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
Hello Dimitry,
Thursday, September 13, 2018, 11:52:08 AM, you wrote:
> I can't reproduce your findings, at least not on a Core i7-4790K:
> type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
> FreeBSD 93454 89077 117328 281016 285456
> Ubuntu
Hello Dimitry,
Thursday, September 13, 2018, 11:52:08 AM, you wrote:
> I can't reproduce your findings, at least not on a Core i7-4790K:
I can not reproduce it on E3-1220v3 + 11-STABLE either. But
security/openssl111 works as expected on J3160 and it bothers me. Something
is wrong not with
On 13 Sep 2018, at 01:46, Lev Serebryakov wrote:
>
> I'm benchmarking new hardware (rather limited one, but still) which
> supports AES-NI (Celeron J3160).
>
> I'm comparing simple "openssl speed aes-256-cbc" and "openssl speed -evp
> aes-256-cbc" on FreeBSD 12-ALPHA4 (built by myself with
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.
On Wed, Sep 12, 2018 at 4:48 PM Lev Serebryakov wrote:
> Hello Brnrd,
>
>I'm benchmarking new hardware (rather limited one, but still) which
> supports AES-NI (Celeron J3160).
>
>I'm comparing simple "openssl speed aes-256-cbc" and "openssl speed -evp
> aes-256-cbc" on FreeBSD
11 matches
Mail list logo
