From: Will Deacon <will.deacon@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
herbert@gondor.apana.org.au, appro@openssl.org
Subject: Re: [PATCH v4] crypto: arm64/sha2: integrate OpenSSL implementations of SHA256/SHA512
Date: Mon, 28 Nov 2016 12:05:04 +0000 [thread overview]
Message-ID: <20161128120503.GC1485@arm.com> (raw)
In-Reply-To: <1479642121-17912-1-git-send-email-ard.biesheuvel@linaro.org>
On Sun, Nov 20, 2016 at 11:42:01AM +0000, Ard Biesheuvel wrote:
> This integrates both the accelerated scalar and the NEON implementations
> of SHA-224/256 as well as SHA-384/512 from the OpenSSL project.
>
> Relative performance compared to the respective generic C versions:
>
> | SHA256-scalar | SHA256-NEON* | SHA512 |
> ------------+-----------------+--------------+----------+
> Cortex-A53 | 1.63x | 1.63x | 2.34x |
> Cortex-A57 | 1.43x | 1.59x | 1.95x |
> Cortex-A73 | 1.26x | 1.56x | ? |
>
> The core crypto code was authored by Andy Polyakov of the OpenSSL
> project, in collaboration with whom the upstream code was adapted so
> that this module can be built from the same version of sha512-armv8.pl.
>
> The version in this patch was taken from OpenSSL commit 32bbb62ea634
> ("sha/asm/sha512-armv8.pl: fix big-endian support in __KERNEL__ case.")
>
> * The core SHA algorithm is fundamentally sequential, but there is a
> secondary transformation involved, called the schedule update, which
> can be performed independently. The NEON version of SHA-224/SHA-256
> only implements this part of the algorithm using NEON instructions,
> the sequential part is always done using scalar instructions.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> arch/arm64/crypto/Kconfig | 8 +
> arch/arm64/crypto/Makefile | 17 +
> arch/arm64/crypto/sha256-core.S_shipped | 2061 ++++++++++++++++++++
> arch/arm64/crypto/sha256-glue.c | 185 ++
> arch/arm64/crypto/sha512-armv8.pl | 778 ++++++++
> arch/arm64/crypto/sha512-core.S_shipped | 1085 +++++++++++
> arch/arm64/crypto/sha512-glue.c | 94 +
> 7 files changed, 4228 insertions(+)
If I build a kernel with this applied and CRYPTO_SHA{256,512}_ARM64=y,
then I end up with untracked .S files according to git:
$ git status
Untracked files:
arch/arm64/crypto/sha256-core.S
arch/arm64/crypto/sha512-core.S
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] crypto: arm64/sha2: integrate OpenSSL implementations of SHA256/SHA512
Date: Mon, 28 Nov 2016 12:05:04 +0000 [thread overview]
Message-ID: <20161128120503.GC1485@arm.com> (raw)
In-Reply-To: <1479642121-17912-1-git-send-email-ard.biesheuvel@linaro.org>
On Sun, Nov 20, 2016 at 11:42:01AM +0000, Ard Biesheuvel wrote:
> This integrates both the accelerated scalar and the NEON implementations
> of SHA-224/256 as well as SHA-384/512 from the OpenSSL project.
>
> Relative performance compared to the respective generic C versions:
>
> | SHA256-scalar | SHA256-NEON* | SHA512 |
> ------------+-----------------+--------------+----------+
> Cortex-A53 | 1.63x | 1.63x | 2.34x |
> Cortex-A57 | 1.43x | 1.59x | 1.95x |
> Cortex-A73 | 1.26x | 1.56x | ? |
>
> The core crypto code was authored by Andy Polyakov of the OpenSSL
> project, in collaboration with whom the upstream code was adapted so
> that this module can be built from the same version of sha512-armv8.pl.
>
> The version in this patch was taken from OpenSSL commit 32bbb62ea634
> ("sha/asm/sha512-armv8.pl: fix big-endian support in __KERNEL__ case.")
>
> * The core SHA algorithm is fundamentally sequential, but there is a
> secondary transformation involved, called the schedule update, which
> can be performed independently. The NEON version of SHA-224/SHA-256
> only implements this part of the algorithm using NEON instructions,
> the sequential part is always done using scalar instructions.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> arch/arm64/crypto/Kconfig | 8 +
> arch/arm64/crypto/Makefile | 17 +
> arch/arm64/crypto/sha256-core.S_shipped | 2061 ++++++++++++++++++++
> arch/arm64/crypto/sha256-glue.c | 185 ++
> arch/arm64/crypto/sha512-armv8.pl | 778 ++++++++
> arch/arm64/crypto/sha512-core.S_shipped | 1085 +++++++++++
> arch/arm64/crypto/sha512-glue.c | 94 +
> 7 files changed, 4228 insertions(+)
If I build a kernel with this applied and CRYPTO_SHA{256,512}_ARM64=y,
then I end up with untracked .S files according to git:
$ git status
Untracked files:
arch/arm64/crypto/sha256-core.S
arch/arm64/crypto/sha512-core.S
Will
next prev parent reply other threads:[~2016-11-28 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1479642121-17912-1-git-send-email-ard.biesheuvel@linaro.org>
2016-11-20 11:43 ` [PATCH v4] crypto: arm64/sha2: integrate OpenSSL implementations of SHA256/SHA512 Ard Biesheuvel
2016-11-20 11:43 ` Ard Biesheuvel
2016-11-28 9:50 ` Ard Biesheuvel
2016-11-28 9:50 ` Ard Biesheuvel
2016-11-28 11:58 ` Herbert Xu
2016-11-28 11:58 ` Herbert Xu
2016-11-28 12:05 ` Will Deacon [this message]
2016-11-28 12:05 ` Will Deacon
2016-11-28 13:17 ` Ard Biesheuvel
2016-11-28 13:17 ` Ard Biesheuvel
2016-11-28 13:32 ` Will Deacon
2016-11-28 13:32 ` Will Deacon
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=20161128120503.GC1485@arm.com \
--to=will.deacon@arm.com \
--cc=appro@openssl.org \
--cc=ard.biesheuvel@linaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.