[dts] [PATCH V2 1/2] add unit_tests_distributor_test_plan

[Liu, Yong]

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 at dpdk.org] On Behalf Of Lijuan Tu
> Sent: Thursday, August 04, 2016 4:09 PM
> To: dts at 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 at 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