From: Will Deacon <will.deacon@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"steve.capper@linaro.org" <steve.capper@linaro.org>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] arm64: crypto: increase AES interleave to 4x
Date: Fri, 20 Feb 2015 15:55:55 +0000 [thread overview]
Message-ID: <20150220155555.GM31692@arm.com> (raw)
In-Reply-To: <1424366716-30439-1-git-send-email-ard.biesheuvel@linaro.org>
On Thu, Feb 19, 2015 at 05:25:16PM +0000, Ard Biesheuvel wrote:
> This patch increases the interleave factor for parallel AES modes
> to 4x. This improves performance on Cortex-A57 by ~35%. This is
> due to the 3-cycle latency of AES instructions on the A57's
> relatively deep pipeline (compared to Cortex-A53 where the AES
> instruction latency is only 2 cycles).
>
> At the same time, disable inline expansion of the core AES functions,
> as the performance benefit of this feature is negligible.
>
> Measured on AMD Seattle (using tcrypt.ko mode=500 sec=1):
>
> Baseline (2x interleave, inline expansion)
> ------------------------------------------
> testing speed of async cbc(aes) (cbc-aes-ce) decryption
> test 4 (128 bit key, 8192 byte blocks): 95545 operations in 1 seconds
> test 14 (256 bit key, 8192 byte blocks): 68496 operations in 1 seconds
>
> This patch (4x interleave, no inline expansion)
> -----------------------------------------------
> testing speed of async cbc(aes) (cbc-aes-ce) decryption
> test 4 (128 bit key, 8192 byte blocks): 124735 operations in 1 seconds
> test 14 (256 bit key, 8192 byte blocks): 92328 operations in 1 seconds
Fine by me. Shall I queue this via the arm64 tree?
Will
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> arch/arm64/crypto/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/crypto/Makefile b/arch/arm64/crypto/Makefile
> index 5720608c50b1..abb79b3cfcfe 100644
> --- a/arch/arm64/crypto/Makefile
> +++ b/arch/arm64/crypto/Makefile
> @@ -29,7 +29,7 @@ aes-ce-blk-y := aes-glue-ce.o aes-ce.o
> obj-$(CONFIG_CRYPTO_AES_ARM64_NEON_BLK) += aes-neon-blk.o
> aes-neon-blk-y := aes-glue-neon.o aes-neon.o
>
> -AFLAGS_aes-ce.o := -DINTERLEAVE=2 -DINTERLEAVE_INLINE
> +AFLAGS_aes-ce.o := -DINTERLEAVE=4
> AFLAGS_aes-neon.o := -DINTERLEAVE=4
>
> CFLAGS_aes-glue-ce.o := -DUSE_V8_CRYPTO_EXTENSIONS
> --
> 1.8.3.2
>
>
next prev parent reply other threads:[~2015-02-20 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 17:25 [PATCH] arm64: crypto: increase AES interleave to 4x Ard Biesheuvel
2015-02-20 15:55 ` Will Deacon [this message]
2015-02-20 16:16 ` Ard Biesheuvel
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=20150220155555.GM31692@arm.com \
--to=will.deacon@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=steve.capper@linaro.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