test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Wan, Zhe" <zhe.wan@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>
Subject: Re: [dts] [PATCH V1 3/4] add config to crypto_perf
Date: Mon, 21 Oct 2019 07:40:29 +0000	[thread overview]
Message-ID: <861C16A15685B44AA870C0D2A97B60458A26C3E3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1571638221-86724-3-git-send-email-bingx.y.yao@intel.com>

Acked-by: Wan, Zhe <zhe.wan@intel.com>




Thanks!
BR,
Wan,Zhe

-----Original Message-----
From: dts <dts-bounces@dpdk.org> On Behalf Of yaobing
Sent: 2019年10月21日 14:10
To: dts@dpdk.org
Cc: Yao, BingX Y <bingx.y.yao@intel.com>
Subject: [dts] [PATCH V1 3/4] add config to crypto_perf

add config to crypto_perf

Signed-off-by: yaobing <bingx.y.yao@intel.com>
---
 conf/crypto_perf_cryptodev_perf.cfg | 149 +++++++++++++++++++++++++---
 1 file changed, 133 insertions(+), 16 deletions(-)

diff --git a/conf/crypto_perf_cryptodev_perf.cfg b/conf/crypto_perf_cryptodev_perf.cfg
index 4e57aba..90c4e4e 100644
--- a/conf/crypto_perf_cryptodev_perf.cfg
+++ b/conf/crypto_perf_cryptodev_perf.cfg
@@ -13,11 +13,142 @@ vdev="crypto_aesni_mb_pmd_1"
 
 total-ops=30000000
 buffer-sz="64,128,256,512,1024,2048"
-optype="cipher-then-auth"
 
+[test_verify_aesni_mb]
+buffer-sz=32
+ptest="verify"
+auth-key-sz=64
+cipher-key-sz=32
+devtype="crypto_aesni_mb"
+cipher-iv-sz=16
+auth-op="generate"
+digest-sz=12
+auth-algo="sha1-hmac"
+cipher-algo="aes-cbc"
+cipher-op="encrypt"
+test-name="sha1_hmac_buff_32"
+test-file="/tmp/test_aes_cbc.data"
+
+[test_verify_qat]
+buffer-sz=32
+ptest="verify"
+auth-key-sz=64
+cipher-key-sz=32
+devtype="crypto_qat"
+cipher-iv-sz=16
+auth-op="generate"
+digest-sz=20
+auth-algo="sha1-hmac"
+cipher-algo="aes-cbc"
+cipher-op="encrypt"
+test-name="sha1_hmac_buff_32"
+test-file="/tmp/test_aes_cbc.data"
+
+[test_verify_openssl_qat]
+l="9,10,11,12"
+vdev="crypto_openssl"
+devtype="crypto_openssl"
+aead-algo="aes-gcm"
+aead-key-sz=16
+aead-iv-sz=12
+aead-op="encrypt"
+aead-aad-sz=16
+digest-sz=16
+optype="aead"
+ptest="verify"
+buffer-sz=32
+test-name="aes_gcm_buff_32"
+test-file="/tmp/test_aes_gcm.data"
+
+[test_verify_openssl]
+l="9,10,11,12"
+vdev="crypto_openssl"
+devtype="crypto_openssl"
+aead-algo="aes-gcm"
+aead-key-sz=16
+aead-iv-sz=12
+aead-op="encrypt"
+aead-aad-sz=16
+digest-sz=16
+optype="aead"
+ptest="verify"
+buffer-sz=32
+test-name="aes_gcm_buff_32"
+test-file="/tmp/test_aes_gcm.data"
+
+[test_latency_qat]
+l="9,10,11,12"
+w="0000:1a:01.0  -w 0000:1a:01.1  -w 0000:1a:01.2"
+devtype="crypto_qat"
+cipher-algo="aes-cbc"
+cipher-key-sz=16
+cipher-iv-sz=16
+cipher-op="encrypt"
+optype="cipher-only"
+ptest="latency"
+
+[test_latency_auth_qat]
+l="9,10,11,12"
+w="0000:1a:01.0  -w 0000:1a:01.1  -w 0000:1a:01.2"
+ptest="latency"
+devtype="crypto_qat"
+cipher-algo="aes-cbc"
+cipher-op="encrypt"
+cipher-key-sz=16
+auth-algo="sha1-hmac"
+auth-op="generate"
+auth-key-sz=64
+digest-sz=12
+silent=None
+
+[test_latency_aead_qat]
+aead-key-sz=16
+optype="aead"
+ptest="latency"
+aead-aad-sz=16
+devtype="crypto_qat"
+aead-op="encrypt"
+digest-sz=16
+aead-algo="aes-gcm"
+aead-iv-sz=12
+
+[test_latency_aesni_gcm]
+vdev="crypto_aesni_gcm_pmd_1"
+aead-key-sz=16
+optype="aead"
+ptest="latency"
+aead-aad-sz=16
+devtype="crypto_aesni_gcm"
+aead-op="encrypt"
+digest-sz=16
+aead-algo="aes-gcm"
+aead-iv-sz=12
+
+[test_latency_auth_aesni_mb]
+l="9,10,11,12"
+vdev="crypto_aesni_mb1 --vdev crypto_aesni_mb2"
+ptest="latency"
+devtype="crypto_aesni_mb"
+cipher-algo="aes-cbc"
+cipher-op="encrypt"
+cipher-key-sz=16
+auth-algo="sha1-hmac"
+auth-op="generate"
+auth-key-sz=64
+silent=None
+digest-sz=12
+
+[test_latency_aesni_mb]
+vdev="crypto_aesni_mb1 --vdev crypto_aesni_mb2"
+devtype="crypto_aesni_mb"
+cipher-algo="aes-cbc"
+cipher-key-sz=16
+cipher-iv-sz=16
+cipher-op="encrypt"
+optype="cipher-only"
+ptest="latency"
 
 [test_qat_aes_cbc_sha1_hmac]
-#test_skip="Y"
 devtype="crypto_qat"
 cipher-algo="aes-cbc"
 cipher-op="encrypt"
@@ -29,8 +160,6 @@ auth-key-sz=64
 digest-sz=20
 
 [test_sw_aes_cbc_sha1_hmac]
-#test_skip="Y"
-total-ops=10000000
 devtype="crypto_aesni_mb"
 cipher-algo="aes-cbc"
 cipher-op="encrypt"
@@ -42,7 +171,6 @@ auth-key-sz=64
 digest-sz=12
 
 [test_qat_aes_cbc_sha2_hmac]
-#test_skip="Y"
 devtype="crypto_qat"
 cipher-algo="aes-cbc"
 cipher-op="encrypt"
@@ -54,8 +182,6 @@ auth-key-sz=64
 digest-sz=32
 
 [test_sw_aes_cbc_sha2_hmac]
-#test_skip="Y"
-total-ops=10000000
 devtype="crypto_aesni_mb"
 cipher-algo="aes-cbc"
 cipher-op="encrypt"
@@ -67,7 +193,6 @@ auth-key-sz=64
 digest-sz=16
 
 [test_qat_aes_gcm]
-#test_skip="Y"
 devtype="crypto_qat"
 optype="aead"
 aead-algo="aes-gcm"
@@ -78,9 +203,7 @@ aead-aad-sz=16
 digest-sz=16
 
 [test_sw_aes_gcm]
-#test_skip="Y"
 vdev="crypto_aesni_gcm_pmd_1"
-total-ops=10000000
 optype="aead"
 devtype="crypto_aesni_gcm"
 aead-algo="aes-gcm"
@@ -91,7 +214,6 @@ aead-aad-sz=16
 digest-sz=16
 
 [test_qat_kasumi]
-#test_skip="Y"
 devtype="crypto_qat"
 cipher-algo="kasumi-f8"
 cipher-op="encrypt"
@@ -103,7 +225,6 @@ auth-key-sz=16
 digest-sz=4
 
 [test_sw_kasumi]
-#test_skip="Y"
 vdev="crypto_kasumi_1"
 total-ops=1000000
 devtype="crypto_kasumi"
@@ -117,7 +238,6 @@ auth-key-sz=16
 digest-sz=4
 
 [test_qat_snow3g]
-#test_skip="Y"
 devtype="crypto_qat"
 cipher-algo="snow3g-uea2"
 cipher-op="encrypt"
@@ -130,7 +250,6 @@ auth-iv-sz=16
 digest-sz=4
 
 [test_sw_snow3g]
-#test_skip="Y"
 vdev="crypto_snow3g_1"
 total-ops=1000000
 devtype="crypto_snow3g"
@@ -145,7 +264,6 @@ auth-iv-sz=16
 digest-sz=4
 
 [test_qat_zuc]
-#test_skip="Y"
 devtype="crypto_qat"
 cipher-algo="zuc-eea3"
 cipher-op="encrypt"
@@ -158,7 +276,6 @@ auth-iv-sz=16
 digest-sz=4
 
 [test_sw_zuc]
-#test_skip="Y"
 vdev="crypto_zuc_1"
 total-ops=1000000
 devtype="crypto_zuc"
-- 
2.17.2


  reply	other threads:[~2019-10-21  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  6:10 [dts] [PATCH V1 1/4] add file " yaobing
2019-10-21  6:10 ` [dts] [PATCH V1 2/4] " yaobing
2019-10-21  7:39   ` Wan, Zhe
2019-10-21  7:44   ` Yao, BingX Y
2019-10-21  6:10 ` [dts] [PATCH V1 3/4] add config " yaobing
2019-10-21  7:40   ` Wan, Zhe [this message]
2019-10-21  7:45   ` Yao, BingX Y
2019-10-21  6:10 ` [dts] [PATCH V1 4/4] tests/TestSuite_crypto_perf_cryptodev_perf: add cases yaobing
2019-10-21  7:40   ` Wan, Zhe
2019-10-21  7:45   ` Yao, BingX Y
2019-10-21  7:39 ` [dts] [PATCH V1 1/4] add file to crypto_perf Wan, Zhe
2019-10-21  7:42   ` Yao, BingX Y
2019-10-23  9:54 ` Tu, Lijuan

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=861C16A15685B44AA870C0D2A97B60458A26C3E3@SHSMSX103.ccr.corp.intel.com \
    --to=zhe.wan@intel.com \
    --cc=bingx.y.yao@intel.com \
    --cc=dts@dpdk.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;
as well as URLs for NNTP newsgroup(s).