From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 9F9B7A0096 for ; Thu, 11 Apr 2019 07:05:06 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 847555B40; Thu, 11 Apr 2019 07:05:06 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 716D25B36 for ; Thu, 11 Apr 2019 07:05:04 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Apr 2019 22:05:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,336,1549958400"; d="scan'208";a="133285166" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga008.jf.intel.com with ESMTP; 10 Apr 2019 22:05:03 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Apr 2019 22:05:02 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.164]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.42]) with mapi id 14.03.0415.000; Thu, 11 Apr 2019 13:05:01 +0800 From: "Zhang, Yuwei1" To: "Ma, LihongX" , "dts@dpdk.org" Thread-Topic: [dts][PATCH V1] rename testplan of eventdev pipeline Thread-Index: AQHU8CPrAnfn+N+Tmkm+hjyXBFCaJaY2Z9Ow Date: Thu, 11 Apr 2019 05:05:00 +0000 Message-ID: References: <1554932617-7936-1-git-send-email-lihongx.ma@intel.com> In-Reply-To: <1554932617-7936-1-git-send-email-lihongx.ma@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOGMyM2NkZmEtYTM0OC00NjdiLWE1M2EtZjg5NGQ1OWQ4Zjg3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiWlJWeXk1TDViMGNsdVRISExHSXlYemxKSWJrZm95UGp3TlJrTmV1bEk3Mm4rWHVVRVFmRmRDZnlIUjA4TGd4bCJ9 dlp-product: dlpe-windows dlp-version: 11.0.600.7 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] rename testplan of eventdev pipeline 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: , Errors-To: dts-bounces@dpdk.org Sender: "dts" Acked by: Yuwei Zhang (yuwei1.zhang@intel.com) -----Original Message----- From: Ma, LihongX=20 Sent: Thursday, April 11, 2019 5:44 AM To: dts@dpdk.org; Zhang, Yuwei1 Cc: Ma, LihongX Subject: [dts][PATCH V1] rename testplan of eventdev pipeline rename sw_eventdev_pipeline_sample_test_plan.rst to eventdev_pipeline_test_= plan.rst and modify some statement format Signed-off-by: lihong --- test_plans/eventdev_pipeline_test_plan.rst | 164 +++++++++++++++++= ++++ .../sw_eventdev_pipeline_sample_test_plan.rst | 151 -----------------= -- 2 files changed, 164 insertions(+), 151 deletions(-) create mode 100644 t= est_plans/eventdev_pipeline_test_plan.rst delete mode 100644 test_plans/sw_eventdev_pipeline_sample_test_plan.rst diff --git a/test_plans/eventdev_pipeline_test_plan.rst b/test_plans/eventd= ev_pipeline_test_plan.rst new file mode 100644 index 0000000..866eae7 --- /dev/null +++ b/test_plans/eventdev_pipeline_test_plan.rst @@ -0,0 +1,164 @@ +.. 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 + +Prerequisites +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + +Test Case: Keep the packets order with default stage in single-flow and=20 +multi-flow=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -s1 -n0 -c32 -W1000 -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=20 +with different 5-tuple(multi-flow) + +3. Observe the packets received by ixia device, ensure packets in each *fl= ow* remain in order, + but note that flows may be re-ordered compared to eachother. + +Test Case: Keep the packets order with one ordered stage in single-flow=20 +and multi-flow=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 on= ly one stage. + +1. Run the sample with below command:: + + # ./build/eventdev_pipeline --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -s1 -n0 -c32 -W1000 -o -D + +2. Send traffic from ixia device with same 5 tuple(single-link) and=20 +with different 5-tuple(multi-flow) + +3. Observe the packets received by ixia device, check the packets order. + +Test Case: Check load-balance behavior with default type in single-flow=20 +and multi-flow situations=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +=3D=3D=3D=3D=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=20 +load-blanced behavior; in single-flow, the load-balanced behavior is=20 +not guaranteed; + +1. Run the sample with below command:: + + # ./build/eventdev_pipeline --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -s1 -n0 -c32 -W1000 -D + +2. Use traffic generator to send huge number of packets: +In single-flow situation, traffic generator will send packets with the=20 +same 5-tuple which is used to calculate rss value; In multi-flow=20 +situation, traffice generator will send packets with different 5-tuple; + +3. Check the load-balance bahavior by the workload of every worker. + +Test Case: Check load-balance behavior with order type stage in=20 +single-flow and multi-flow situations=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +=3D=3D=3D=3D=3D=3D=3D=3D=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 si= ngle-flow and multi-flow situations. + +1. Run the sample with below command:: + + # ./build/eventdev_pipeline --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -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=20 +same 5-tuple which is used to calculate rss value; In multi-flow=20 +situation, traffice generator will send packets with different 5-tuple; + +3. Check the load-balance bahavior by the workload of every worker. + +Test Case: Check load-balance behavior with parallel type stage in=20 +single-flow and multi-flow situations=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 si= ngle-flow and multi-flow situations. + +1. Run the sample with below command:: + + # ./build/eventdev_pipeline --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -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=20 +same 5-tuple which is used to calculate rss value; In multi-flow=20 +situation, traffic generator will send packets with different 5-tuple; + +3. Check the load-balance bahavior by the workload of every worker. + +Test Case: Performance test for default type of stage=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=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 --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -s2 -n0 -c32 + +2. use traffic generator to send huge number of packets(with same=20 +5-tuple and different 5-tuple) + +3. observe the speed of packets received. + +Test Case: Performance test for parallel type of stage=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=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 parallel type of stage in singl= e-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 --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -s2 -n0 -c32 -p + +2. use traffic generator to send huge number of packets(with same=20 +5-tuple and different 5-tuple) + +3. observe the speed of packets received. + +Test Case: Performance test for ordered type of stage=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=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 ordered 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 --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -s2 -n0 -c32 -o + +2. use traffic generator to send huge number of packets(with same=20 +5-tuple and different 5-tuple) + +3. observe the speed of packets received. + +Test Case: Basic forward test for all type of stage=20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=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 basic forward test with all type of stage. + +1. Run the sample with below command:: + + # ./build/eventdev_pipeline --vdev event_sw0 -- -r2 -t4 -e8 -w F0=20 + -s1 -n0 -c32 + +2. use traffic generator to send some packets and verify the sample=20 +could forward them normally diff --git a/test_plans/sw_eventdev_pipeline_sample_test_plan.rst b/test_pl= ans/sw_eventdev_pipeline_sample_test_plan.rst deleted file mode 100644 index fba6915..0000000 --- a/test_plans/sw_eventdev_pipeline_sample_test_plan.rst +++ /dev/null @@ -1,151 +0,0 @@ -.. 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 - -Prerequisites -=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-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=3D=3D=3D=3D=3D -Description: the sample only guarantee that keep the packets order with on= ly 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:=20 --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 d= ifferent 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 m= ulti-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 d= ifferent 5-tuple(multi-flow) - -3. Observe the packets received by ixia device, ensure packets in each *fl= ow* remain in order, but note that flows may be re-ordered compared to each= other. - - -Test Case 3: Check load-balance behavior with atomic type in single-flow a= nd 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-blanc= ed 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 sam= e 5-tuple which is used to calculate rss value; -In multi-flow situation, t= raffice 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-f= low 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 si= ngle-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 sam= e 5-tuple which is used to calculate rss value; -In multi-flow situation, t= raffice 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 singl= e-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 si= ngle-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 sam= e 5-tuple which is used to calculate rss value; -In multi-flow situation, t= raffic 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-tuple = 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-tuple = 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-tuple = and different 5-tuple) - -3. observe the speed of packets received. - -Test Case 9: Basic forward test for all 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 -Description: Execute basic forward test with all type of stage. - -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 some packets and verify the sample could = forward them normally - -- 2.7.4