From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
x86@kernel.org
Subject: Re: [PATCH 0/2] lib/crypto: x86/sha512: Partially roll up loops
Date: Fri, 13 Nov 2026 20:25:51 -0800 [thread overview]
Message-ID: <20261114042551.GG2025@sol> (raw)
In-Reply-To: <20261112082839.414786-1-ebiggers@kernel.org>
On Thu, Nov 12, 2026 at 12:28:37AM -0800, Eric Biggers wrote:
> Some freshly baked loop rolls in the SSSE3 and AVX optimized SHA-512
> code.
>
> In each file, SHA-512 rounds 14 through 77 are rolled up into 8 groups
> of 8 rounds. This saves 20.2 KB of text. It's also likely to increase
> performance on the CPUs that actually run this code (i.e., CPUs without
> AVX2), due to the improved use of the cache, though the oldest I was
> able to confirm that on is Haswell which has AVX2 anyway.
>
> Eric Biggers (2):
> lib/crypto: x86/sha512: Partially roll up sha512_transform_avx()
> lib/crypto: x86/sha512: Partially roll up sha512_transform_ssse3()
>
> lib/crypto/x86/sha512-avx-asm.S | 124 +++++++++++++++--------------
> lib/crypto/x86/sha512-ssse3-asm.S | 126 ++++++++++++++++--------------
> 2 files changed, 135 insertions(+), 115 deletions(-)
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next
- Eric
prev parent reply other threads:[~2026-11-14 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:28 [PATCH 0/2] lib/crypto: x86/sha512: Partially roll up loops Eric Biggers
2026-11-12 8:28 ` [PATCH 1/2] lib/crypto: x86/sha512: Partially roll up sha512_transform_avx() Eric Biggers
2026-11-13 8:33 ` Ard Biesheuvel
2026-11-12 8:28 ` [PATCH 2/2] lib/crypto: x86/sha512: Partially roll up sha512_transform_ssse3() Eric Biggers
2026-11-13 8:34 ` Ard Biesheuvel
2026-11-14 4:25 ` Eric Biggers [this message]
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=20261114042551.GG2025@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--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.