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>,
Martin Willi <martin@strongswan.org>,
Antonio Quartulli <antonio@mandelbit.com>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH] lib/crypto: tests: Add some additional lengths to the ChaCha benchmark
Date: Wed, 4 Nov 2026 15:06:26 -0800 [thread overview]
Message-ID: <20261104230626.87060-1-ebiggers@kernel.org> (raw)
All the benchmarked lengths below 1420 are multiples of the ChaCha block
size, and all except 64 are a multiple of 4 blocks. Add some additional
lengths to cover a wider variety of situations.
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
lib/crypto/tests/chacha_kunit.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/crypto/tests/chacha_kunit.c b/lib/crypto/tests/chacha_kunit.c
index bbf73dcbafee..2e002e46976e 100644
--- a/lib/crypto/tests/chacha_kunit.c
+++ b/lib/crypto/tests/chacha_kunit.c
@@ -217,7 +217,8 @@ static void test_chacha_rfc7539(struct kunit *test)
static void benchmark_chacha(struct kunit *test)
{
static const size_t lens_to_test[] = {
- 64, 256, 512, 1024, 1420, 2048, 4096, 8920, 16384,
+ 64, 128, 200, 256, 511, 512, 513,
+ 1024, 1420, 2048, 4096, 8920, 16384,
};
const size_t max_len = 16384;
u8 *data = alloc_buf(test, max_len);
base-commit: 9fbbbaefd5f95551da18426c200cf41e1b4255a1
--
2.56.0
next reply other threads:[~2026-11-04 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 23:06 Eric Biggers [this message]
2026-11-05 15:33 ` [PATCH] lib/crypto: tests: Add some additional lengths to the ChaCha benchmark Antonio Quartulli
2026-11-07 21:06 ` Eric Biggers
2026-11-07 22:06 ` 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=20261104230626.87060-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=antonio@mandelbit.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=martin@strongswan.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