From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-crypto@vger.kernel.org
Cc: ebiggers@kernel.org, Ard Biesheuvel <ard.biesheuvel@linaro.org>,
herbert@gondor.apana.org.au,
linux-arm-kernel@lists.infradead.org, steve.capper@arm.com
Subject: [PATCH 0/2] crypto: arm64/aes-ce - implement 5-way interleave for some modes
Date: Mon, 24 Jun 2019 19:38:29 +0200 [thread overview]
Message-ID: <20190624173831.8375-1-ard.biesheuvel@linaro.org> (raw)
As it turns out, even a 4-way interleave is not sufficient to saturate
the ThunderX2 pipeline with AES instructions, so this series implements
5-way interleave for modes that can be modified without running out of
registers to maintain chaining mode state across the encryption operation,
i.e., ECB, CBC-decryption and CTR.
Ard Biesheuvel (2):
crypto: arm64/aes-ce - add 5 way interleave routines
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
arch/arm64/crypto/aes-ce.S | 60 ++++++----
arch/arm64/crypto/aes-modes.S | 118 +++++++++++++++-----
arch/arm64/crypto/aes-neon.S | 48 +-------
3 files changed, 127 insertions(+), 99 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-06-24 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 17:38 Ard Biesheuvel [this message]
2019-06-24 17:38 ` [PATCH 1/2] crypto: arm64/aes-ce - add 5 way interleave routines Ard Biesheuvel
2019-06-24 17:38 ` [PATCH 2/2] crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR Ard Biesheuvel
2019-07-03 14:27 ` [PATCH 0/2] crypto: arm64/aes-ce - implement 5-way interleave for some modes 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=20190624173831.8375-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=steve.capper@arm.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).