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.
________________________________ From: 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 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 -evp aes-128-cbc will tell you if the code uses hardware acceleration, as it's only the EVP that is accelerated. 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? With 1.0.1 and 1.0.2 I'm getting around 100000k/s with and without EVP, so that looks like a regression to me. -- Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com<http://www.cz.redhat.com> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
