From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Thorsten Blum <thorsten.blum@linux.dev>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
David Laight <david.laight@runbox.com>,
David Sterba <dsterba@suse.com>,
llvm@lists.linux.dev, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] lib/crypto: blake2b: Roll up BLAKE2b round loop on 32-bit
Date: Thu, 4 Dec 2025 12:56:32 -0500 [thread overview]
Message-ID: <aTHLUIjqCHlRs8rr@zx2c4.com> (raw)
In-Reply-To: <20251203190652.144076-1-ebiggers@kernel.org>
On Wed, Dec 03, 2025 at 11:06:52AM -0800, Eric Biggers wrote:
> G(r, 4, v[0], v[ 5], v[10], v[15]); \
> G(r, 5, v[1], v[ 6], v[11], v[12]); \
> G(r, 6, v[2], v[ 7], v[ 8], v[13]); \
> G(r, 7, v[3], v[ 4], v[ 9], v[14]); \
> } while (0)
> - ROUND(0);
> - ROUND(1);
> - ROUND(2);
> - ROUND(3);
> - ROUND(4);
> - ROUND(5);
> - ROUND(6);
> - ROUND(7);
> - ROUND(8);
> - ROUND(9);
> - ROUND(10);
> - ROUND(11);
> +
> +#ifdef CONFIG_64BIT
> + /*
> + * Unroll the rounds loop to enable constant-folding of the
> + * blake2b_sigma values. Seems worthwhile on 64-bit kernels.
> + * Not worthwhile on 32-bit kernels because the code size is
> + * already so large there due to BLAKE2b using 64-bit words.
> + */
> + unrolled_full
> +#endif
> + for (int r = 0; r < 12; r++)
> + ROUND(r);
>
> #undef G
> #undef ROUND
Since you're now using `unrolled_full`, ROUND doesn't need to be a macro
anymore. You can just do:
unrolled_full
for (int r = 0; r < 12; r++) {
G(r, 0, v[0], v[ 4], v[ 8], v[12]);
G(r, 1, v[1], v[ 5], v[ 9], v[13]);
G(r, 2, v[2], v[ 6], v[10], v[14]);
G(r, 3, v[3], v[ 7], v[11], v[15]);
G(r, 4, v[0], v[ 5], v[10], v[15]);
G(r, 5, v[1], v[ 6], v[11], v[12]);
G(r, 6, v[2], v[ 7], v[ 8], v[13]);
G(r, 7, v[3], v[ 4], v[ 9], v[14]);
}
Likewise, you can simplify the blake2s implementation in the same way
(but don't make the unrolled_full conditional there, obviously).
`unrolled_full` seems like a nice way of doing this compared to macros.
Jason
next prev parent reply other threads:[~2025-12-04 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 19:06 [PATCH] lib/crypto: blake2b: Roll up BLAKE2b round loop on 32-bit Eric Biggers
2025-12-04 9:05 ` Ard Biesheuvel
2025-12-04 17:56 ` Jason A. Donenfeld [this message]
2025-12-05 4:58 ` Eric Biggers
2025-12-05 14:16 ` david laight
2025-12-05 20:14 ` Eric Biggers
2025-12-05 22:04 ` david laight
2025-12-26 20:24 ` david laight
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=aTHLUIjqCHlRs8rr@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=david.laight@runbox.com \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=justinstitt@google.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=thorsten.blum@linux.dev \
/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