From: Patrick Robb <probb@iol.unh.edu>
To: Kai Ji <kai.ji@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com
Subject: Re: [dpdk-dev v1] app/test-crypto-perf: remove decrypt test case from perf
Date: Sun, 4 May 2025 17:17:18 -0400 [thread overview]
Message-ID: <CAJvnSUACcmKUhZZSa_AZkn0kGChb-wbbbpiqT9m2qPOCmqnLcg@mail.gmail.com> (raw)
In-Reply-To: <20250502101226.1405274-1-kai.ji@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3157 bytes --]
Please disregard the Community Lab DTS failure just reported on this
patchseries. I need to reconfigure the testbed and rerun the test.
On Fri, May 2, 2025 at 6:12 AM Kai Ji <kai.ji@intel.com> wrote:
> Remove all decrypt test cases in aesni-mb throughput perf as the
> decrypt throughput testing only support OOP by dpdk-test-crypto-perf
>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> ---
> .../configs/crypto-perf-aesni-mb.json | 24 -------------------
> 1 file changed, 24 deletions(-)
>
> diff --git a/app/test-crypto-perf/configs/crypto-perf-aesni-mb.json
> b/app/test-crypto-perf/configs/crypto-perf-aesni-mb.json
> index d50e4af36c..91fbc9cfcd 100644
> --- a/app/test-crypto-perf/configs/crypto-perf-aesni-mb.json
> +++ b/app/test-crypto-perf/configs/crypto-perf-aesni-mb.json
> @@ -13,13 +13,6 @@
> "devtype": "crypto_aesni_mb"
> }
> },
> - "AES-CBC-128 SHA1-HMAC auth-then-cipher decrypt": {
> - "cipher-algo": "aes-cbc",
> - "cipher-key-sz": "16",
> - "auth-algo": "sha1-hmac",
> - "optype": "auth-then-cipher",
> - "cipher-op": "decrypt"
> - },
> "AES-CBC-128 SHA1-HMAC cipher-then-auth encrypt": {
> "cipher-algo": "aes-cbc",
> "cipher-key-sz": "16",
> @@ -30,13 +23,6 @@
> "optype": "cipher-then-auth",
> "cipher-op": "encrypt"
> },
> - "AES-CBC-256 SHA2-256-HMAC auth-then-cipher decrypt": {
> - "cipher-algo": "aes-cbc",
> - "cipher-key-sz": "32",
> - "auth-algo": "sha2-256-hmac",
> - "optype": "auth-then-cipher",
> - "cipher-op": "decrypt"
> - },
> "AES-CBC-256 SHA2-256-HMAC cipher-then-auth encrypt": {
> "cipher-algo": "aes-cbc",
> "cipher-key-sz": "32",
> @@ -53,21 +39,11 @@
> "optype": "aead",
> "total-ops": "10000000"
> },
> - "AES-GCM-128 aead-op decrypt": {
> - "aead-algo": "aes-gcm",
> - "aead-key-sz": "16",
> - "aead-op": "decrypt"
> - },
> "AES-GCM-256 aead-op encrypt": {
> "aead-algo": "aes-gcm",
> "aead-key-sz": "32",
> "aead-op": "encrypt"
> },
> - "AES-GCM-256 aead-op decrypt": {
> - "aead-algo": "aes-gcm",
> - "aead-key-sz": "32",
> - "aead-op": "decrypt"
> - },
> "AES-GMAC 128 auth-only generate": {
> "auth-algo": "aes-gmac",
> "auth-key-sz": "16",
> --
> 2.34.1
>
>
[-- Attachment #2: Type: text/html, Size: 4830 bytes --]
next prev parent reply other threads:[~2025-05-04 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 10:12 Kai Ji
2025-05-04 21:17 ` Patrick Robb [this message]
2025-05-07 8:56 ` Radu Nicolau
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=CAJvnSUACcmKUhZZSa_AZkn0kGChb-wbbbpiqT9m2qPOCmqnLcg@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).