mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Antonio Quartulli <antonio@mandelbit.com>
Cc: Martin Willi <martin@strongswan.org>,
	"Jason A . Donenfeld" <Jason@zx2c4.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] lib/crypto: x86/chacha: Add 16-block AVX-512 implementation
Date: Mon, 26 Oct 2026 11:36:53 -0700	[thread overview]
Message-ID: <20261026183653.GA1876@quark> (raw)
In-Reply-To: <3e2dee91-bba4-42e3-9d22-619ea54484e4@mandelbit.com>

On Mon, Oct 26, 2026 at 01:46:19AM +0100, Antonio Quartulli wrote:
> Patch 1 (KUnit tests and benchmark for chacha_crypt()) is independent
> of the AVX-512 code: it compares chacha_crypt() against
> chacha_block_generic() for every length up to 4100 bytes and random
> ones up to 12 KiB, with guard pages, in-place and split calls, plus the
> RFC 7539 vector.
> 
> @Eric, would you consider it on its own? It would cover Martin's series
> as well. I can resend it standalone if that's easier.

I'm interested in the KUnit test, and I'll review patch 1 when I have a
chance.  No need to resend it yet.

- Eric

      reply	other threads:[~2026-10-26 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 23:47 Antonio Quartulli
2026-10-25 23:47 ` [PATCH 1/2] lib/crypto: tests: Add KUnit tests and benchmark for ChaCha Antonio Quartulli
2026-10-27  1:53   ` Eric Biggers
2026-10-27  8:51     ` Antonio Quartulli
2026-10-25 23:47 ` [PATCH 2/2] lib/crypto: x86/chacha: Add 16-block AVX-512 (zmm) implementation Antonio Quartulli
2026-10-26  0:35 ` [PATCH 0/2] lib/crypto: x86/chacha: Add 16-block AVX-512 implementation Eric Biggers
2026-10-26  0:46   ` Antonio Quartulli
2026-10-26 18:36     ` 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=20261026183653.GA1876@quark \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=antonio@mandelbit.com \
    --cc=ardb@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®