From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2] crypto: x86/aes-gcm - add VAES and AVX512 / AVX10 optimized AES-GCM
Date: Mon, 20 May 2024 09:16:07 -0700 [thread overview]
Message-ID: <20240520161607.GA1269@sol.localdomain> (raw)
In-Reply-To: <20240512073124.53568-1-ebiggers@kernel.org>
On Sun, May 12, 2024 at 12:31:24AM -0700, Eric Biggers wrote:
> Table 3: VAES-based AES-256-GCM encryption throughput in MB/s,
> implementation name vs. message length in bytes:
>
> | 16384 | 4096 | 4095 | 1420 | 512 | 500 |
> ---------------------+-------+-------+-------+-------+-------+-------+
> This implementation | 13139 | 12070 | 11466 | 8999 | 6949 | 6048 |
> AVX512_Intel_OpenSSL | 12927 | 11499 | 10976 | 8375 | 5386 | 5853 |
> AVX512_Intel_Linux | 12656 | 11263 | 10779 | 7958 | 5592 | 5029 |
> AVX512_Cloudflare | 11120 | 10186 | 10075 | 4856 | 4919 | 4786 |
>
> | 300 | 200 | 64 | 63 | 16 |
> ---------------------+-------+-------+-------+-------+-------+
> This implementation | 4709 | 3512 | 1787 | 1765 | 714 |
> AVX512_Intel_OpenSSL | 4157 | 4071 | 2493 | 2132 | 1042 |
> AVX512_Intel_Linux | 3535 | 2686 | 1416 | 1203 | 572 |
> AVX512_Cloudflare | 3062 | 1110 | 1042 | 1028 | 169 |
>
Note, some of the AVX512_Cloudflare numbers were slightly off, and I've fixed
this in v3. v3 also includes another small optimization.
- Eric
prev parent reply other threads:[~2024-05-20 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 7:31 [PATCH v2] crypto: x86/aes-gcm - add VAES and AVX512 / AVX10 optimized AES-GCM Eric Biggers
2024-05-20 16:16 ` 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=20240520161607.GA1269@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox