From: "Wan, Zhe" <zhe.wan@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>,
"Zhao, XinfengX" <xinfengx.zhao@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
Subject: Re: [dts] [PATCH V1 3/3] conf: add test setting for aes-docsisbpi cases
Date: Wed, 27 May 2020 08:07:22 +0000 [thread overview]
Message-ID: <DM5PR11MB2059E63CF07E33EAEDC05522EEB10@DM5PR11MB2059.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200515080332.102832-4-xinfengx.zhao@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 xinfengx
Sent: 2020年5月15日 16:04
To: dts@dpdk.org
Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
Subject: [dts] [PATCH V1 3/3] conf: add test setting for aes-docsisbpi cases
Signed-off-by: xinfengx <xinfengx.zhao@intel.com>
---
conf/crypto_perf_cryptodev_perf.cfg | 38 ++++++++++++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/conf/crypto_perf_cryptodev_perf.cfg b/conf/crypto_perf_cryptodev_perf.cfg
index 90c4e4e..05dc6af 100644
--- a/conf/crypto_perf_cryptodev_perf.cfg
+++ b/conf/crypto_perf_cryptodev_perf.cfg
@@ -9,7 +9,7 @@ n=6
# default crypto device and sw device config, it could be overrided by test case w="0000:1a:01.0"
-vdev="crypto_aesni_mb_pmd_1"
+vdev="crypto_aesni_mb_1"
total-ops=30000000
buffer-sz="64,128,256,512,1024,2048"
@@ -213,6 +213,42 @@ aead-iv-sz=12
aead-aad-sz=16
digest-sz=16
+[test_qat_encrypt_aes_docsisbpi]
+devtype="crypto_qat"
+cipher-algo="aes-docsisbpi"
+cipher-op="encrypt"
+optype="cipher-only"
+cipher-key-sz=32
+cipher-iv-sz=16
+buffer-sz="40,64,70,128,256,512,1024,2048"
+
+[test_sw_encrypt_aes_docsisbpi]
+devtype="crypto_aesni_mb"
+cipher-algo="aes-docsisbpi"
+cipher-op="encrypt"
+optype="cipher-only"
+cipher-key-sz=32
+cipher-iv-sz=16
+buffer-sz="40,64,70,128,256,512,1024,2048"
+
+[test_qat_decrypt_aes_docsisbpi]
+devtype="crypto_qat"
+cipher-algo="aes-docsisbpi"
+cipher-op="decrypt"
+optype="cipher-only"
+cipher-key-sz=32
+cipher-iv-sz=16
+buffer-sz="40,64,70,128,256,512,1024,2048"
+
+[test_sw_decrypt_aes_docsisbpi]
+devtype="crypto_aesni_mb"
+cipher-algo="aes-docsisbpi"
+cipher-op="decrypt"
+optype="cipher-only"
+cipher-key-sz=32
+cipher-iv-sz=16
+buffer-sz="40,64,70,128,256,512,1024,2048"
+
[test_qat_kasumi]
devtype="crypto_qat"
cipher-algo="kasumi-f8"
--
2.17.1
next prev parent reply other threads:[~2020-05-27 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 8:03 [dts] [PATCH V1 0/3] add new test cases for aes-docsisbpi xinfengx
2020-05-15 8:03 ` [dts] [PATCH V1 1/3] test_plans: add aes-docsisbpi algorithm into crypto_perf test plan xinfengx
2020-05-15 8:03 ` [dts] [PATCH V1 2/3] tests: add test cases for aes-docsisbpi xinfengx
2020-05-15 8:03 ` [dts] [PATCH V1 3/3] conf: add test setting for aes-docsisbpi cases xinfengx
2020-05-27 8:07 ` Wan, Zhe [this message]
2020-05-26 7:45 ` [dts] [PATCH V1 0/3] add new test cases for aes-docsisbpi Zhao, XinfengX
2020-06-01 7:46 ` 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=DM5PR11MB2059E63CF07E33EAEDC05522EEB10@DM5PR11MB2059.namprd11.prod.outlook.com \
--to=zhe.wan@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=xinfengx.zhao@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).