From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-crypto@vger.kernel.org
Cc: Ondrej Mosnacek <omosnace@redhat.com>,
herbert@gondor.apana.org.au,
linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH v2 0/2] crypto: aegis128 SIMD improvements
Date: Mon, 14 Oct 2019 18:16:43 +0200 [thread overview]
Message-ID: <20191014161645.1961-1-ard.biesheuvel@linaro.org> (raw)
Refactor the aegis128 code to get rid of indirect calls, and implement
SIMD versions of the init() and final() hooks. This results in a ~2x
speedup on ARM Cortex-A57 for ~1500 byte inputs.
Changes since v1:
- fix missing Sbox loads for plain SIMD on GCC
- fix endianness issue in final_simd() routine
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Ard Biesheuvel (2):
crypto: aegis128 - avoid function pointers for parameterization
crypto: aegis128 - duplicate init() and final() hooks in SIMD code
crypto/aegis128-core.c | 125 ++++++++++----------
crypto/aegis128-neon-inner.c | 50 ++++++++
crypto/aegis128-neon.c | 21 ++++
3 files changed, 134 insertions(+), 62 deletions(-)
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-10-14 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 16:16 Ard Biesheuvel [this message]
2019-10-14 16:16 ` [PATCH v2 1/2] crypto: aegis128 - avoid function pointers for parameterization Ard Biesheuvel
2019-10-14 16:16 ` [PATCH v2 2/2] crypto: aegis128 - duplicate init() and final() hooks in SIMD code Ard Biesheuvel
2019-10-25 15:18 ` [PATCH v2 0/2] crypto: aegis128 SIMD improvements Herbert Xu
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=20191014161645.1961-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=omosnace@redhat.com \
/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).