From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: Stefan Kanthak <stefan.kanthak@nexgo.de>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] crypto: x86/sha256-ni - cleanup and optimization
Date: Tue, 9 Apr 2024 08:42:14 -0400 [thread overview]
Message-ID: <20240409124216.9261-1-ebiggers@kernel.org> (raw)
This patchset reduces the amount of source code duplication in
sha256_ni_asm.S and also reduces the binary code size slightly.
Eric Biggers (2):
crypto: x86/sha256-ni - convert to use rounds macros
crypto: x86/sha256-ni - optimize code size
arch/x86/crypto/sha256_ni_asm.S | 242 +++++++-------------------------
1 file changed, 47 insertions(+), 195 deletions(-)
base-commit: 4ad27a8be9dbefd4820da0f60da879d512b2f659
--
2.44.0
next reply other threads:[~2024-04-09 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 12:42 Eric Biggers [this message]
2024-04-09 12:42 ` [PATCH 1/2] crypto: x86/sha256-ni - convert to use rounds macros Eric Biggers
2024-04-09 16:52 ` Stefan Kanthak
2024-04-09 23:36 ` Eric Biggers
2024-04-11 7:42 ` Stefan Kanthak
2024-04-11 16:16 ` Eric Biggers
2024-04-09 12:42 ` [PATCH 2/2] crypto: x86/sha256-ni - optimize code size 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=20240409124216.9261-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.kanthak@nexgo.de \
/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