From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] crypto: arm64/ghash-ce - performance improvements
Date: Sat, 4 Aug 2018 20:46:23 +0200 [thread overview]
Message-ID: <20180804184625.28523-1-ard.biesheuvel@linaro.org> (raw)
Another bit of performance work on the GHASH driver: this time it is not
the combined AES/GCM algorithm but the bare GHASH driver that gets updated.
Even though ARM cores that implement the polynomical multiplication
instructions that these routines depend on are guaranteed to also support
the AES instructions, and can thus use the AES/GCM driver, there could
be reasons to use the accelerated GHASH in isolation, e.g., with another
symmetric blockcipher, with a faster h/w accelerator, or potentially with
an accelerator that does not expose the AES key to the OS.
The resulting code runs at 1.1 cycles per byte on Cortex-A53 (down from
2.4 cycles per byte)
Ard Biesheuvel (2):
crypto: arm64/ghash-ce - replace NEON yield check with block limit
crypto: arm64/ghash-ce - implement 4-way aggregation
arch/arm64/crypto/ghash-ce-core.S | 153 ++++++++++++++------
arch/arm64/crypto/ghash-ce-glue.c | 87 ++++++-----
2 files changed, 161 insertions(+), 79 deletions(-)
--
2.18.0
next reply other threads:[~2018-08-04 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 18:46 Ard Biesheuvel [this message]
2018-08-04 18:46 ` [PATCH 1/2] crypto: arm64/ghash-ce - replace NEON yield check with block limit Ard Biesheuvel
2018-08-04 18:46 ` [PATCH 2/2] crypto: arm64/ghash-ce - implement 4-way aggregation Ard Biesheuvel
2018-08-07 9:53 ` [PATCH 0/2] crypto: arm64/ghash-ce - performance 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=20180804184625.28523-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).