From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: x86@kernel.org
Subject: [PATCH 0/7] crypto: x86 - minor optimizations and cleanup to VAES code
Date: Tue, 10 Dec 2024 15:58:27 -0800 [thread overview]
Message-ID: <20241210235834.40862-1-ebiggers@kernel.org> (raw)
This series contains a few minor optimizations and cleanups for the
VAES-optimized AES-XTS and AES-GCM code.
Eric Biggers (7):
crypto: x86/aes-gcm - code size optimization
crypto: x86/aes-gcm - tune better for AMD CPUs
crypto: x86/aes-xts - use .irp when useful
crypto: x86/aes-xts - make the register aliases per-function
crypto: x86/aes-xts - improve some comments
crypto: x86/aes-xts - change len parameter to int
crypto: x86/aes-xts - more code size optimizations
arch/x86/crypto/aes-gcm-avx10-x86_64.S | 119 +++++++----------
arch/x86/crypto/aes-xts-avx-x86_64.S | 178 +++++++++++--------------
arch/x86/crypto/aesni-intel_glue.c | 10 +-
3 files changed, 134 insertions(+), 173 deletions(-)
base-commit: f04be1dddc70fcdd01497d66786e748106271eb6
--
2.47.1
next reply other threads:[~2024-12-10 23:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 23:58 Eric Biggers [this message]
2024-12-10 23:58 ` [PATCH 1/7] crypto: x86/aes-gcm - code size optimization Eric Biggers
2024-12-10 23:58 ` [PATCH 2/7] crypto: x86/aes-gcm - tune better for AMD CPUs Eric Biggers
2024-12-10 23:58 ` [PATCH 3/7] crypto: x86/aes-xts - use .irp when useful Eric Biggers
2024-12-10 23:58 ` [PATCH 4/7] crypto: x86/aes-xts - make the register aliases per-function Eric Biggers
2024-12-10 23:58 ` [PATCH 5/7] crypto: x86/aes-xts - improve some comments Eric Biggers
2024-12-10 23:58 ` [PATCH 6/7] crypto: x86/aes-xts - change len parameter to int Eric Biggers
2024-12-10 23:58 ` [PATCH 7/7] crypto: x86/aes-xts - more code size optimizations 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=20241210235834.40862-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@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 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.