From: Eric Biggers <ebiggers@kernel.org>
To: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, qat-linux@intel.com,
stable@vger.kernel.org
Subject: Re: [PATCH] crypto: qat - lower priority for skcipher and aead algorithms
Date: Mon, 16 Jun 2025 21:25:49 +0000 [thread overview]
Message-ID: <20250616212549.GB23807@google.com> (raw)
In-Reply-To: <20250616164752.GB1373@sol>
On Mon, Jun 16, 2025 at 09:47:52AM -0700, Eric Biggers wrote:
> FWIW, on an AMD EPYC 9B45 (Zen 5 / Turin) server processor, I get 35.2 GB/s.
> This processor appeared to run at about 4.15 GHz, so that's about 8.5 bytes per
> cycle. That's 51% more bytes per cycle than Intel. This shows that there is
> still room for improvement in VAES, even when it's already much better than QAT.
Also, to be clear, the 35.2 GB/s (and the corresponding bytes/cycle number of
8.5) is single-thread throughput. This should have been clear since I compared
it to the single-thread throughput on Emerald Rapids. But I just wanted to make
sure to state it explicitly, as an earlier part of my email discussed
whole-processor throughput which it could be confused with.
- Eric
next prev parent reply other threads:[~2025-06-16 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 10:32 [PATCH] crypto: qat - lower priority for skcipher and aead algorithms Giovanni Cabiddu
2025-06-13 19:01 ` Eric Biggers
2025-06-13 19:28 ` Eric Biggers
2025-06-16 4:18 ` Herbert Xu
2025-06-16 15:02 ` Giovanni Cabiddu
2025-06-16 16:47 ` Eric Biggers
2025-06-16 16:54 ` Eric Biggers
2025-06-16 21:25 ` Eric Biggers [this message]
2025-06-17 4:57 ` Herbert Xu
2025-06-19 20:21 ` Giovanni Cabiddu
2025-06-23 9:20 ` Herbert Xu
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=20250616212549.GB23807@google.com \
--to=ebiggers@kernel.org \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=stable@vger.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.