* [dts] [PATCH V2 0/2] Add packet distributor unit test plan and test script
@ 2016-08-04 8:04 Lijuan Tu
2016-08-04 8:09 ` [dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan Lijuan Tu
2016-08-04 8:10 ` [dts] [PATCH V2 2/2] add unit_tests_distributor test script Lijuan Tu
0 siblings, 2 replies; 4+ messages in thread
From: Lijuan Tu @ 2016-08-04 8:04 UTC (permalink / raw)
To: dts; +Cc: Lijuan Tu
Lijuan Tu (2):
add unit_tests_distributor_test_plan
add unit_tests_distributor test script
test_plans/unit_tests_distributor_test_plan.rst | 104 ++++++++++++++++++++
tests/TestSuite_unit_tests_distributor.py | 125 ++++++++++++++++++++++++
2 files changed, 229 insertions(+)
create mode 100644 test_plans/unit_tests_distributor_test_plan.rst
create mode 100644 tests/TestSuite_unit_tests_distributor.py
--
1.9.3
^ permalink raw reply [flat|nested] 4+ messages in thread
* [dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan
2016-08-04 8:04 [dts] [PATCH V2 0/2] Add packet distributor unit test plan and test script Lijuan Tu
@ 2016-08-04 8:09 ` Lijuan Tu
2016-08-04 8:53 ` Liu, Yong
2016-08-04 8:10 ` [dts] [PATCH V2 2/2] add unit_tests_distributor test script Lijuan Tu
1 sibling, 1 reply; 4+ messages in thread
From: Lijuan Tu @ 2016-08-04 8:09 UTC (permalink / raw)
To: dts; +Cc: Lijuan Tu
Signed-off-by: Lijuan Tu <lijuanx.a.tu@intel.com>
---
test_plans/unit_tests_distributor_test_plan.rst | 104 ++++++++++++++++++++++++
1 file changed, 104 insertions(+)
create mode 100644 test_plans/unit_tests_distributor_test_plan.rst
diff --git a/test_plans/unit_tests_distributor_test_plan.rst b/test_plans/unit_tests_distributor_test_plan.rst
new file mode 100644
index 0000000..c25533d
--- /dev/null
+++ b/test_plans/unit_tests_distributor_test_plan.rst
@@ -0,0 +1,104 @@
+.. Copyright (c) <2014>, Intel Corporation
+ All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ - Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ - Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+
+ - Neither the name of Intel Corporation nor the names of its
+ contributors may be used to endorse or promote products derived
+ from this software without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+ FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+ (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Prerequisites
+=============
+One 10Gb Ethernet port of the DUT is directly connected and link is up.
+
+===================
+Packet Distributor
+===================
+The DPDK Packet Distributor library is a library designed to be used for
+dynamic load balancing of traffic while supporting single packet at a
+time operation. When using this library, the logical cores in use are to
+be considered in two roles: firstly a distributor lcore, which is
+responsible for load balancing or distributing packets, and a set of
+worker lcores which are responsible for receiving the packets from the
+distributor and operating on them.
+
+This is the test plan for Packet Distributor unit test.
+
+This section explains how to run the unit tests for distributor.
+The test can be launched independently using the command line interface.
+This test is implemented as a linuxapp environment application.
+
+The complete test suite is launched automatically using a python-expect
+script (launched using ``make test``) that sends commands to
+the application and checks the results. A test report is displayed on
+stdout.
+
+The final output of the test will be average cycles of IO used per packet.
+
+The steps to run the unit test manually are as follow::
+
+ # make -C ./app/test/
+ # ./app/test/test -n 1 -c ffff
+ RTE>> distributor_autotest
+
+suppose we test 1 distributor core and n worker cores::
+
+number of cores will be n+1
+
+===============================================
+Test Case: 1 distributor core and 1 worker core
+===============================================
+number of cores is 2::
+
+ ./app/test/test -n 1 -c 0xC
+
+================================================
+Test Case: 1 distributor core and 4 worker cores
+================================================
+number of cores is 5::
+
+ ./app/test/test -n 1 -c 0x3e
+
+================================================
+Test Case: 1 distributor core and 8 worker cores
+================================================
+number of cores is 9::
+
+ ./app/test/test -n 1 -c 0x3fe
+
+================================================
+Test Case: 1 distributor core and 5 worker cores
+================================================
+number of cores is 6::
+
+ ./app/test/test -n 1 -c 0x7e
+================================================
+Test Case: 1 distributor core and 10 worker core
+================================================
+number of cores is 11::
+
+ ./app/test/test -n 1 -c 0xffe
+
--
1.9.3
^ permalink raw reply [flat|nested] 4+ messages in thread
* [dts] [PATCH V2 2/2] add unit_tests_distributor test script
2016-08-04 8:04 [dts] [PATCH V2 0/2] Add packet distributor unit test plan and test script Lijuan Tu
2016-08-04 8:09 ` [dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan Lijuan Tu
@ 2016-08-04 8:10 ` Lijuan Tu
1 sibling, 0 replies; 4+ messages in thread
From: Lijuan Tu @ 2016-08-04 8:10 UTC (permalink / raw)
To: dts; +Cc: Lijuan Tu
Signed-off-by: Lijuan Tu <lijuanx.a.tu@intel.com>
---
tests/TestSuite_unit_tests_distributor.py | 125 ++++++++++++++++++++++++++++++
1 file changed, 125 insertions(+)
create mode 100644 tests/TestSuite_unit_tests_distributor.py
diff --git a/tests/TestSuite_unit_tests_distributor.py b/tests/TestSuite_unit_tests_distributor.py
new file mode 100644
index 0000000..9a4c709
--- /dev/null
+++ b/tests/TestSuite_unit_tests_distributor.py
@@ -0,0 +1,125 @@
+# BSD LICENSE
+#
+# Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
+# All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions
+# are met:
+#
+# * Redistributions of source code must retain the above copyright
+# notice, this list of conditions and the following disclaimer.
+# * Redistributions in binary form must reproduce the above copyright
+# notice, this list of conditions and the following disclaimer in
+# the documentation and/or other materials provided with the
+# distribution.
+# * Neither the name of Intel Corporation nor the names of its
+# contributors may be used to endorse or promote products derived
+# from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+"""
+DPDK Test suite.
+
+This TestSuite runs the unit tests included in DPDK for power feature.
+"""
+import dts
+
+from test_case import TestCase
+
+#
+#
+# Test class.
+#
+
+
+class TestUnitTestsDistributor(TestCase):
+
+ #
+ #
+ #
+ # Test cases.
+ #
+
+ def set_up_all(self):
+ """
+ Run at the start of each test suite.
+ """
+ self.verify(self.dut.number_of_cores > 11, "Don't have enough cores")
+ out = self.dut.build_dpdk_apps('./app/test/')
+ self.verify('make: Leaving directory' in out, "Compilation failed")
+
+ def set_up(self):
+ """
+ Run before each test case.
+ """
+ pass
+
+ def distributor_autotest(self, core_list):
+ """
+ Run unit test: distributor_autotest
+ """
+ core_mask = dts.create_mask(core_list)
+ self.dut.send_expect("./app/test/test -n 4 -c %s" % core_mask, "R.*T.*E.*>.*>", 60)
+ out = self.dut.send_expect("distributor_autotest", "RTE>>", 60)
+ self.dut.send_expect("quit", "# ")
+ self.verify("Test OK" in out, "Test failed")
+
+
+ def test_1_distributor_1_worker(self):
+ """
+ 1 distributor core and 1 worker core.
+ """
+ cores = self.dut.get_core_list("1S/2C/1T")
+ self.distributor_autotest(cores)
+
+ def test_1_distributor_4_worker(self):
+ """
+ 1 distributor core and 4 worker cores.
+ """
+ cores = self.dut.get_core_list("1S/5C/1T")
+ self.distributor_autotest(cores)
+
+ def test_1_distributor_8_worker(self):
+ """
+ 1 distributor core and 8 worker cores.
+ """
+ cores = self.dut.get_core_list("1S/9C/1T")
+ self.distributor_autotest(cores)
+
+ def test_1_distributor_10_worker(self):
+ """
+ 1 distributor core and 10 worker cores.
+ """
+ cores = self.dut.get_core_list("1S/11C/1T")
+ self.distributor_autotest(cores)
+
+ def test_1_distributor_5_worker(self):
+ """
+ 1 distributor core and 5 worker cores.
+ """
+ cores = self.dut.get_core_list("1S/6C/1T")
+ self.distributor_autotest(cores)
+
+ def tear_down(self):
+ """
+ Run after each test case.
+ """
+ pass
+
+ def tear_down_all(self):
+ """
+ Run after each test suite.
+ """
+ pass
--
1.9.3
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan
2016-08-04 8:09 ` [dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan Lijuan Tu
@ 2016-08-04 8:53 ` Liu, Yong
0 siblings, 0 replies; 4+ messages in thread
From: Liu, Yong @ 2016-08-04 8:53 UTC (permalink / raw)
To: Tu, LijuanX A, dts; +Cc: Tu, LijuanX A
Lijuan, just one simple question. Why this suite choose 1,4,5,8,10 distributors, is there any logic related?
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Lijuan Tu
> Sent: Thursday, August 04, 2016 4:09 PM
> To: dts@dpdk.org
> Cc: Tu, LijuanX A
> Subject: [dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan
>
> Signed-off-by: Lijuan Tu <lijuanx.a.tu@intel.com>
> ---
> test_plans/unit_tests_distributor_test_plan.rst | 104
> ++++++++++++++++++++++++
> 1 file changed, 104 insertions(+)
> create mode 100644 test_plans/unit_tests_distributor_test_plan.rst
>
> diff --git a/test_plans/unit_tests_distributor_test_plan.rst
> b/test_plans/unit_tests_distributor_test_plan.rst
> new file mode 100644
> index 0000000..c25533d
> --- /dev/null
> +++ b/test_plans/unit_tests_distributor_test_plan.rst
> @@ -0,0 +1,104 @@
> +.. Copyright (c) <2014>, Intel Corporation
> + All rights reserved.
> +
> + Redistribution and use in source and binary forms, with or without
> + modification, are permitted provided that the following conditions
> + are met:
> +
> + - Redistributions of source code must retain the above copyright
> + notice, this list of conditions and the following disclaimer.
> +
> + - Redistributions in binary form must reproduce the above copyright
> + notice, this list of conditions and the following disclaimer in
> + the documentation and/or other materials provided with the
> + distribution.
> +
> + - Neither the name of Intel Corporation nor the names of its
> + contributors may be used to endorse or promote products derived
> + from this software without specific prior written permission.
> +
> + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
> + FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
> + COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
> + INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> + (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> + SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
> + STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> + ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
> + OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +Prerequisites
> +=============
> +One 10Gb Ethernet port of the DUT is directly connected and link is up.
> +
> +===================
> +Packet Distributor
> +===================
> +The DPDK Packet Distributor library is a library designed to be used for
> +dynamic load balancing of traffic while supporting single packet at a
> +time operation. When using this library, the logical cores in use are to
> +be considered in two roles: firstly a distributor lcore, which is
> +responsible for load balancing or distributing packets, and a set of
> +worker lcores which are responsible for receiving the packets from the
> +distributor and operating on them.
> +
> +This is the test plan for Packet Distributor unit test.
> +
> +This section explains how to run the unit tests for distributor.
> +The test can be launched independently using the command line interface.
> +This test is implemented as a linuxapp environment application.
> +
> +The complete test suite is launched automatically using a python-expect
> +script (launched using ``make test``) that sends commands to
> +the application and checks the results. A test report is displayed on
> +stdout.
> +
> +The final output of the test will be average cycles of IO used per packet.
> +
> +The steps to run the unit test manually are as follow::
> +
> + # make -C ./app/test/
> + # ./app/test/test -n 1 -c ffff
> + RTE>> distributor_autotest
> +
> +suppose we test 1 distributor core and n worker cores::
> +
> +number of cores will be n+1
> +
> +===============================================
> +Test Case: 1 distributor core and 1 worker core
> +===============================================
> +number of cores is 2::
> +
> + ./app/test/test -n 1 -c 0xC
> +
> +================================================
> +Test Case: 1 distributor core and 4 worker cores
> +================================================
> +number of cores is 5::
> +
> + ./app/test/test -n 1 -c 0x3e
> +
> +================================================
> +Test Case: 1 distributor core and 8 worker cores
> +================================================
> +number of cores is 9::
> +
> + ./app/test/test -n 1 -c 0x3fe
> +
> +================================================
> +Test Case: 1 distributor core and 5 worker cores
> +================================================
> +number of cores is 6::
> +
> + ./app/test/test -n 1 -c 0x7e
> +================================================
> +Test Case: 1 distributor core and 10 worker core
> +================================================
> +number of cores is 11::
> +
> + ./app/test/test -n 1 -c 0xffe
> +
> --
> 1.9.3
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-08-04 8:53 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-04 8:04 [dts] [PATCH V2 0/2] Add packet distributor unit test plan and test script Lijuan Tu
2016-08-04 8:09 ` [dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan Lijuan Tu
2016-08-04 8:53 ` Liu, Yong
2016-08-04 8:10 ` [dts] [PATCH V2 2/2] add unit_tests_distributor test script Lijuan Tu
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).