From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] crypto: x86 - AES-CTR and AES-XCTR rewrite
Date: Tue, 4 Feb 2025 19:50:24 -0800 [thread overview]
Message-ID: <20250205035026.116976-1-ebiggers@kernel.org> (raw)
This series adds new implementations of AES-CTR and AES-XCTR that are
optimized for modern x86_64 CPUs, and it removes the existing
implementations that are superseded or obsolete.
Changed in v2:
- Split the removal of the non-AVX implementation of AES-CTR into a
separate patch, and removed the assembly code too.
- Made some minor tweaks to the new assembly file, including fixing a
build error when aesni-intel is built as a module.
Eric Biggers (2):
crypto: x86/aes-ctr - rewrite AES-NI optimized CTR and add VAES
support
crypto: x86/aes-ctr - remove non-AVX implementation of AES-CTR
arch/x86/crypto/Makefile | 2 +-
arch/x86/crypto/aes-ctr-avx-x86_64.S | 552 ++++++++++++++++++++++
arch/x86/crypto/aes_ctrby8_avx-x86_64.S | 597 ------------------------
arch/x86/crypto/aesni-intel_asm.S | 125 -----
arch/x86/crypto/aesni-intel_glue.c | 450 ++++++++----------
5 files changed, 756 insertions(+), 970 deletions(-)
create mode 100644 arch/x86/crypto/aes-ctr-avx-x86_64.S
delete mode 100644 arch/x86/crypto/aes_ctrby8_avx-x86_64.S
base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
--
2.48.1
next reply other threads:[~2025-02-05 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 3:50 Eric Biggers [this message]
2025-02-05 3:50 ` [PATCH 1/2] crypto: x86/aes-ctr - rewrite AES-NI optimized CTR and add VAES support Eric Biggers
2025-02-05 3:50 ` [PATCH 2/2] crypto: x86/aes-ctr - remove non-AVX implementation of AES-CTR Eric Biggers
2025-02-08 3:12 ` Eric Biggers
2025-02-05 3:55 ` [PATCH 0/2] crypto: x86 - AES-CTR and AES-XCTR rewrite Eric Biggers
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=20250205035026.116976-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox