From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libressl: add assembly for aarch64, ppc*, extra assembly for arm
Date: Fri, 24 Jul 2020 03:52:14 +0200 [thread overview]
Message-ID: <20200724015214.mmlNFykXyH08Sk53qXbIz9-w-lSKwTfP0QQkRUyYJsA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23655@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
There's a merged pull request on the void-packages repository
libressl: add assembly for aarch64, ppc*, extra assembly for arm
https://github.com/void-linux/void-packages/pull/23655
Description:
This yields significant speedups (20x) in some things (AES/ghash) on platforms with hardware crypto support (e.g. POWER8 and newer, and most aarch64) as well as enhances performance of assorted alogrithms by using optimized assembly implementations instead of portable fallbacks. E.g. on aarch64 https://gist.githubusercontent.com/q66/c75a46fc7d0c27eff21cc9d70639bf95/raw/dde1f60e304ef8f4a4049d41388d9c25e63b4a1e/gistfile1.txt
As it is now, libressl only supports asm for x86(_64) and to a limited degree, 32-bit ARM. The extra support was added by my project: https://github.com/q66/libressl-portable-asm
Everything was tested, test suite passes on all platforms, and benchmarks were run on relevant hardware, confirming the speedups.
I still think we should move back to OpenSSL, since there are many reasons to do so (even disregarding performance) and the performance is still better on it (as there are various algos that don't have optimized implementations under libressl at all) but this could be a decent stopgap solution, enabling at least basic things (like hardware AES on non-x86 systems).
Tested:
- [x] ppc64le
- [x] ppc64
- [x] ppc
- [x] armv7l
- [x] aarch64
Benchmarked:
- [x] ppc64le
- [x] ppc64
- [x] ppc
- [x] armv7l
- [x] aarch64
@void-linux/pkg-committers
prev parent reply other threads:[~2020-07-24 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 21:46 [PR PATCH] [RFC] " q66
2020-07-19 22:19 ` [PR PATCH] [Updated] " q66
2020-07-19 22:22 ` q66
2020-07-19 23:29 ` q66
2020-07-20 0:03 ` ahesford
2020-07-23 15:49 ` [PR PATCH] [Updated] " q66
2020-07-23 21:38 ` q66
2020-07-24 1:52 ` q66 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200724015214.mmlNFykXyH08Sk53qXbIz9-w-lSKwTfP0QQkRUyYJsA@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).