From: Zhe <zhe.wan@intel.com>
To: dts@dpdk.org
Cc: Zhe Wan <zhe.wan@intel.com>
Subject: [dts] [PATCH V1] test_plans: add test cases for compressdev_zlib_pmd
Date: Tue, 26 Nov 2019 05:04:37 -0500 [thread overview]
Message-ID: <1574762677-68855-1-git-send-email-zhe.wan@intel.com> (raw)
From: Zhe Wan <zhe.wan@intel.com>
Signed-off-by: Zhe Wan <zhe.wan@intel.com>
---
test_plans/compressdev_zlib_pmd_test_plan.rst | 42 +++++++++++++++++++++++++--
1 file changed, 39 insertions(+), 3 deletions(-)
diff --git a/test_plans/compressdev_zlib_pmd_test_plan.rst b/test_plans/compressdev_zlib_pmd_test_plan.rst
index b7284e4..b52c6f4 100644
--- a/test_plans/compressdev_zlib_pmd_test_plan.rst
+++ b/test_plans/compressdev_zlib_pmd_test_plan.rst
@@ -65,14 +65,50 @@ Start test application and run zlib pmd unit test::
Verify all test cases passed in the test.
-Test Case: Compressdev ZLIB PMD test
----------------------------------------------------------
+Test Case: Compressdev ZLIB PMD fixed function test
+-------------------------------------------------------------
Run Compressdev zlib pmd test with below sample commands::
./app/dpdk-test-compress-perf -w vdev_bus_id -l 4 \
--vdev=compress_zlib -- --driver-name compress_zlib --input-file file_name \
--compress-level level --num-iter number --huffman-enc fixed
-Perform the test with huffman-enc fixed and dynamic accordingly.
+Perform the test with fixed huffman-enc.
Test all the file types in calgary corpus, all files should pass the test.
+
+Test Case: Compressdev ZLIB PMD dynamic function test
+-------------------------------------------------------------
+Run Compressdev zlib pmd test with below sample commands::
+
+ ./app/dpdk-test-compress-perf -w vdev_bus_id -l 4 \
+ --vdev=compress_zlib -- --driver-name compress_zlib --input-file file_name \
+ --compress-level level --num-iter number --huffman-enc fixed
+
+Perform the test with dynamic huffman-enc.
+
+Test all the file types in calgary corpus, all files should pass the test.
+
+Test Case: Compressdev ZLIB PMD fixed performance test
+----------------------------------------------------------------------------
+Run Compressdev zlib pmd performance test with below sample commands::
+
+ ./app/dpdk-test-compress-perf -w vdev_bus_id -l 4 \
+ --vdev=compress_zlib -- --driver-name compress_zlib --input-file file_name \
+ --compress-level level --seg-sz size --num-iter number --huffman-enc fixed
+
+Perform the test with fixed huffman-enc and calgary file.
+
+Run the test with seg-sz 1k, 2k, 4k, 8k, 16k and 32k respectively.
+
+Test Case: Compressdev ZLIB PMD dynamic performance test
+---------------------------------------------------------------------------
+Run Compressdev zlib pmd performance test with below sample commands::
+
+ ./app/dpdk-test-compress-perf -w vdev_bus_id -l 4 \
+ --vdev=compress_zlib -- --driver-name compress_zlib --input-file file_name \
+ --compress-level level --seg-sz size --num-iter number --huffman-enc dynamic
+
+Perform the test with dynamic huffman-enc and calgary file.
+
+Run the test with seg-sz 1k, 2k, 4k, 8k, 16k and 32k respectively.
--
1.8.3.1
next reply other threads:[~2019-11-26 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 10:04 Zhe [this message]
2019-11-27 9:37 ` Tu, Lijuan
2019-11-26 14:59 Zhe
2019-11-27 9:39 ` 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=1574762677-68855-1-git-send-email-zhe.wan@intel.com \
--to=zhe.wan@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).