From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 719B11B33B for ; Fri, 10 Nov 2017 06:36:16 +0100 (CET) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Nov 2017 21:36:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,372,1505804400"; d="scan'208";a="174638718" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga006.fm.intel.com with ESMTP; 09 Nov 2017 21:36:03 -0800 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 9 Nov 2017 21:36:02 -0800 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx110.amr.corp.intel.com (10.18.116.10) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 9 Nov 2017 21:36:02 -0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.159]) with mapi id 14.03.0319.002; Fri, 10 Nov 2017 13:36:00 +0800 From: "Liu, Yong" To: "Zhang, Yuwei1" , "dts@dpdk.org" CC: "Zhang, Yuwei1" Thread-Topic: [dts] [PATCH V1] Add sw eventdev test plan Thread-Index: AQHTU+qIw/PWV9fybkqkFN/yKTx8L6MNIqcQ Date: Fri, 10 Nov 2017 05:36:00 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62F147C5@SHSMSX103.ccr.corp.intel.com> References: <20171102145336.4596-1-yuwei1.zhang@intel.com> In-Reply-To: <20171102145336.4596-1-yuwei1.zhang@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDVmYjE1YzQtNjMxZS00YzZiLTg3NjctNmE5Njc4MjJjOWYyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiI3R2VxYjNOcTFOc3lBRERxaERMbTRSTEtcL2YzSTVrSEFmZjdsU2VBUUhpR2h4clpxUDVtc3lJRWY3K1wvMTFmUDUifQ== x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V1] Add sw eventdev test plan X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2017 05:36:17 -0000 Yuwei, Please add some descriptions in the header of the test plan. I saw that all test cases depend on IXIA. Could we make those cases suitabl= e for software packet generator like scapy? Not everyone has expensive hardware instrument. For those who just want to = check the basic status of eventdev, few thousands of packets are enough.=20 Thanks, Marvin > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yuwei Zhang > Sent: Thursday, November 02, 2017 10:54 PM > To: dts@dpdk.org > Cc: Zhang, Yuwei1 > Subject: [dts] [PATCH V1] Add sw eventdev test plan >=20 > add software eventdev test plan >=20 > Signed-off-by: Yuwei Zhang > --- > .../sw_eventdev_pipeline_sample_test_plan.rst | 140 > +++++++++++++++++++++ > 1 file changed, 140 insertions(+) > create mode 100644 test_plans/sw_eventdev_pipeline_sample_test_plan.rst >=20 > diff --git a/test_plans/sw_eventdev_pipeline_sample_test_plan.rst > b/test_plans/sw_eventdev_pipeline_sample_test_plan.rst > new file mode 100644 > index 0000000..926adf0 > --- /dev/null > +++ b/test_plans/sw_eventdev_pipeline_sample_test_plan.rst > @@ -0,0 +1,140 @@ > +.. Copyright (c) <2013-2017>, 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. > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D > +Eventdev Pipeline SW PMD Tests > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D > + > +Prerequistites > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > +Test Case 1: Keep the packets order with one ordered stage in single-flo= w > and multi-flow > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +Description: the sample only guarantee that keep the packets order with > only one stage. > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s1 -n0 -c32 -W1000 -o -D > +Parameters: > +-r2, -t4, -e8: allocate cores to rx, tx and shedular > +-w: allocate cores to workers > +-s1: the sample only contain 1 stage > +-n0: the sample will run forever without a packets num limit > + > +2. Send traffic from ixia device with same 5 tuple(single-link) and with > different 5-tuple(multi-flow) > + > +3. Observe the packets received by ixia device, check the packets order. > + > +Test Case 2: Keep the packets order with atomic stage in single-flow and > multi-flow > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +Description: the packets' order which will pass through a same flow > should be guaranteed. > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s2 -n0 -c32 -W1000 -a -D > + > +2. Send traffic from ixia device with same 5 tuple(single-link) and with > different 5-tuple(multi-flow) > + > +3. Observe the packets received by ixia device, ensure packets in each > *flow* remain in order, but note that flows may be re-ordered compared to > eachother. > + > + > +Test Case 3: Check load-balance behavior with atomic type in single-flow > and multi-flow situations > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D > +Description: In multi-flow situation, sample should have a good load- > blanced behavior; in single-flow, the load-balanced behavior is not > guaranteed; > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s1 -n0 -c32 -W1000 -a -D > + > +2. Use traffic generator to send huge number of packets: > +In single-flow situation, traffic generator will send packets with the > same 5-tuple which is used to calculate rss value; > +In multi-flow situation, traffice generator will send packets with > different 5-tuple; > + > +3. Check the load-balance bahavior by the workload of every worker. > + > +Test Case 4: Check load-balance behavior with order type stage in single= - > flow and multi-flow situations > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D > +Description: A good load-balanced behavior should be guaranteed in both > single-flow and multi-flow situations. > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s1 -n0 -c32 -W1000 -o -D > + > +2. Use traffic generator to send huge number of packets: > +In single-flow situation, traffic generator will send packets with the > same 5-tuple which is used to calculate rss value; > +In multi-flow situation, traffice generator will send packets with > different 5-tuple; > + > +3. Check the load-balance bahavior by the workload of every worker. > + > +Test Case 5: Check load-balance behavior with parallel type stage in > single-flow and multi-flow situations > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D > +Description: A good load-balanced behavior should be guaranteed in both > single-flow and multi-flow situations. > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s1 -n0 -c32 -W1000 -p -D > + > +2. Use traffic generator to send huge number of packets: > +In single-flow situation, traffic generator will send packets with the > same 5-tuple which is used to calculate rss value; > +In multi-flow situation, traffic generator will send packets with > different 5-tuple; > + > +3. Check the load-balance bahavior by the workload of every worker. > + > +Test Case 6: Performance test for atomic type of stage > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D > +Description: Execute performance test with atomic type of stage in > single-flow and multi-flow situation. > +We use 4 worker and 2 stage as the test background. > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s1 -n0 -c32 > + > +2. use traffic generator to send huge number of packets(with same 5-tupl= e > and different 5-tuple) > + > +3. observe the speed of packets received. > + > +Test Case 7: Performance test for parallel type of stage > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D > +Description: Execute performance test with atomic type of stage in > single-flow and multi-flow situation. > +We use 4 worker and 2 stage as the test background. > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s1 -n0 -c32 > + > +2. use traffic generator to send huge number of packets(with same 5-tupl= e > and different 5-tuple) > + > +3. observe the speed of packets received. > + > +Test Case 8: Performance test for ordered type of stage > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D > +Description: Execute performance test with atomic type of stage in > single-flow and multi-flow situation. > +We use 4 worker and 2 stage as the test background. > + > +1. Run the sample with below command: > +# ./build/eventdev_pipeline_sw_pmd --vdev event_sw0 -- -r2 -t4 -e8 -w F0 > -s1 -n0 -c32 > + > +2. use traffic generator to send huge number of packets(with same 5-tupl= e > and different 5-tuple) > + > +3. observe the speed of packets received. > \ No newline at end of file > -- > 2.14.1.windows.1