Re: [openssl-dev] arch (ARM) capabilities

2016-06-28 Thread Hubert Kario
On Tuesday 28 June 2016 14:35:52 Andy Polyakov wrote: > >>> But when I've tested it on AArch64 with openssl-1.1.0-pre5 and > >>> current master (./configure no-shared no-engine) I'm getting > >>> 100524.03k vs 52172.12k/s in favour of the non-EVP version. > >>> > >>> Is that really expected? > >>

Re: [openssl-dev] arch (ARM) capabilities

2016-06-28 Thread Andy Polyakov
>>> But when I've tested it on AArch64 with openssl-1.1.0-pre5 and >>> current master (./configure no-shared no-engine) I'm getting >>> 100524.03k vs 52172.12k/s in favour of the non-EVP version. >>> >>> Is that really expected? >> >> Depends on your system. Not all AArch64 processors were born

Re: [openssl-dev] arch (ARM) capabilities

2016-06-28 Thread Hubert Kario
On Monday 27 June 2016 17:20:39 Andy Polyakov wrote: > >> Is there an option when making an app that uses OpenSSL to verify > >> that is uses Crypto Extensions (like checking a flag or something > >> like that) ? > > > > With x86_64, ciphers like aes-128-cbc are much faster with AES-NI, > > so a

Re: [openssl-dev] arch (ARM) capabilities

2016-06-28 Thread Andy Polyakov
>> I want something more programmatic, more general. I want to deliver >> a piece of software that will run on ARM architectures and will >> issue a warning or something like that if the user does not have an >> OpenSSL library set to work with ARM Crypto Extension. > > What does "set to work"

Re: [openssl-dev] arch (ARM) capabilities

2016-06-27 Thread Andy Polyakov
> I want something more programmatic, more general. > I want to deliver a piece of software that will run on ARM architectures and > will issue a warning or something like that if the user does not have an > OpenSSL library set to work with ARM Crypto Extension. What does "set to work" mean?

Re: [openssl-dev] arch (ARM) capabilities

2016-06-27 Thread Andy Polyakov
>> Is there an option when making an app that uses OpenSSL to verify >> that is uses Crypto Extensions (like checking a flag or something >> like that) ? > > With x86_64, ciphers like aes-128-cbc are much faster with AES-NI, > so a simple benchmark: > > openssl speed aes-128-cbc openssl speed

Re: [openssl-dev] arch (ARM) capabilities

2016-06-27 Thread Catalin Vasile
: Hubert Kario <hka...@redhat.com> Sent: Monday, June 27, 2016 5:11:57 PM To: openssl-dev@openssl.org Cc: Catalin Vasile Subject: Re: [openssl-dev] arch (ARM) capabilities On Monday 27 June 2016 12:37:39 Catalin Vasile wrote: > Hi, > > Is there an option when making an app th

Re: [openssl-dev] arch (ARM) capabilities

2016-06-27 Thread Catalin Vasile
com> Sent: Monday, June 27, 2016 5:11 PM To: openssl-dev@openssl.org Cc: Catalin Vasile Subject: Re: [openssl-dev] arch (ARM) capabilities   On Monday 27 June 2016 12:37:39 Catalin Vasile wrote: > Hi, > > Is there an option when making an app that uses OpenSSL > to verify t

Re: [openssl-dev] arch (ARM) capabilities

2016-06-27 Thread Hubert Kario
On Monday 27 June 2016 12:37:39 Catalin Vasile wrote: > Hi, > > Is there an option when making an app that uses OpenSSL > to verify that is uses Crypto Extensions (like checking > a flag or something like that) ? With x86_64, ciphers like aes-128-cbc are much faster with AES-NI, so a simple

[openssl-dev] arch (ARM) capabilities

2016-06-27 Thread Catalin Vasile
Hi, Is there an option when making an app that uses OpenSSL to verify that is uses Crypto Extensions (like checking a flag or something like that) ? Cata -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev