test suite reviews and discussions
 help / color / mirror / Atom feed
From: Xinfeng Zhao <xinfengx.zhao@intel.com>
To: dts@dpdk.org
Cc: Xinfeng Zhao <xinfengx.zhao@intel.com>
Subject: [dts] [PATCH V1] test_plan: add new feature in cryptodev unit test_plan
Date: Wed,  5 Jun 2019 01:24:11 +0800	[thread overview]
Message-ID: <1559669051-205557-1-git-send-email-xinfengx.zhao@intel.com> (raw)

add case "cryptodev_qat_asym_autotest"

Signed-off-by: Xinfeng Zhao <xinfengx.zhao@intel.com>
---
 test_plans/unit_tests_cryptodev_func_test_plan.rst | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/test_plans/unit_tests_cryptodev_func_test_plan.rst b/test_plans/unit_tests_cryptodev_func_test_plan.rst
index 6cb6c5e..836a6b7 100644
--- a/test_plans/unit_tests_cryptodev_func_test_plan.rst
+++ b/test_plans/unit_tests_cryptodev_func_test_plan.rst
@@ -45,7 +45,7 @@ Technology) into DPDK. The QAT provides poll mode crypto driver support for
 Intel@ QuickAssist Adapter 8950 hardware accelerator.
 
 The testing of Crytpodev API should be tested under either Intel QuickAssist Technology DH895xxC hardware
-accelerator or AES-NI library.
+accelerator or AES-NI, KASUMI, SNOW3G, ZUC library.
 
 This test suite will run all cryptodev related unit test cases. Alternatively, you could execute
 the unit tests manually by app/test DPDK application.
@@ -62,16 +62,28 @@ Unit Test List
 - cryptodev_sw_kasumi_autotest
 - cryptodev_sw_zuc_autotest
 - cryptodev_scheduler_autotest
+- cryptodev_qat_asym_autotest
 
 
 Test Case Setup
 ===============
 
+#. Enable crypto PMD in config/common_base
+
+     CONFIG_RTE_LIBRTE_PMD_QAT_SYM
+     CONFIG_RTE_LIBRTE_PMD_QAT_ASYM
+     CONFIG_RTE_LIBRTE_PMD_AESNI_MB
+     CONFIG_RTE_LIBRTE_PMD_AESNI_GCM
+     CONFIG_RTE_LIBRTE_PMD_OPENSSL
+     CONFIG_RTE_LIBRTE_PMD_KASUMI
+     CONFIG_RTE_LIBRTE_PMD_SNOW3G
+     CONFIG_RTE_LIBRTE_PMD_ZUC
+
 #. Build DPDK and app/test app
 #. Bind cryptodev devices to igb_uio driver
 #. Manually verify the app/test by this command, as example, in your build folder::
 
-     ./app/test -c 1 -n 1
+     ./app/test -c 1 -n 1 -w 0000:1a:01.0
      RTE>> cryptodev_qat_autotest
 
 All Unit Test Cases are listed above.
-- 
2.7.4


                 reply	other threads:[~2019-06-05  2:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1559669051-205557-1-git-send-email-xinfengx.zhao@intel.com \
    --to=xinfengx.zhao@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).