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 4C92EA00E6 for ; Wed, 12 Jun 2019 08:38:52 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id F28961D13F; Wed, 12 Jun 2019 08:38:51 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by dpdk.org (Postfix) with ESMTP id 101811D12C for ; Wed, 12 Jun 2019 08:38:50 +0200 (CEST) Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5C6agZO015097; Tue, 11 Jun 2019 23:38:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=pfpt0818; bh=ITdTwSGQUNpC1eV91rh4JCIZVltr/929dy90zKi2jPA=; b=UgQ0dSKUzHTPDLdNh6/1DmHjp2DtYStZejEW/m0wjfRLLXaIyvdpiG1kuAHw6sE4LNhC 9y48LWxBy7ScBwVcW7c3JcsE0n/ajo6vgUUS5GiroVu7X8SjaDbLZMctHLgrRusX4Wrb EOAX4AUTw6tWoi1KYBSs6djA+m1nDTN1iIOMXMFbZJeK1tzu9yhGHKPmrYbz6/LDjOxx 6ghddiaB3rj3aetWSiLsvf2VLf3EXhAd4IYAQ+GUs3unHMfT8t4i9yHP8resLAxNKHUm 5vKh/xsiZIXLS+pySRmHoljsCxhfNcHMeIPit9ifTGPMG9aOSO+O9OnBy5pnyNicpZD9 Rw== Received: from sc-exch02.marvell.com ([199.233.58.182]) by mx0b-0016f401.pphosted.com with ESMTP id 2t2r828vx7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 11 Jun 2019 23:38:49 -0700 Received: from SC-EXCH03.marvell.com (10.93.176.83) by SC-EXCH02.marvell.com (10.93.176.82) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 11 Jun 2019 23:38:48 -0700 Received: from NAM04-CO1-obe.outbound.protection.outlook.com (104.47.45.59) by SC-EXCH03.marvell.com (10.93.176.83) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Tue, 11 Jun 2019 23:38:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.onmicrosoft.com; s=selector2-marvell-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ITdTwSGQUNpC1eV91rh4JCIZVltr/929dy90zKi2jPA=; b=E9RgLy/Myi8HLXLjf9aGMwvA7nMkvK1PZXA2ZZafcTc5GGEHWu/FCvqfiNvWjJXkFeto+a4ZAgff/NgAqTK994+u2rCp6fyAxmHiIzrET83bQn83tnsRHe6/sNzAzkK3WDSeNdnRRhkjajsaoPAZ4nTKhEADfARxdtZfL7fJ+XY= Received: from MN2PR18MB2735.namprd18.prod.outlook.com (20.178.255.222) by MN2PR18MB3408.namprd18.prod.outlook.com (10.255.238.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.12; Wed, 12 Jun 2019 06:38:43 +0000 Received: from MN2PR18MB2735.namprd18.prod.outlook.com ([fe80::9049:5e7f:4161:8cc7]) by MN2PR18MB2735.namprd18.prod.outlook.com ([fe80::9049:5e7f:4161:8cc7%6]) with mapi id 15.20.1965.017; Wed, 12 Jun 2019 06:38:43 +0000 From: Thanseerul Haq To: "Tu, Lijuan" , "dts@dpdk.org" CC: Faisal Masood , Vijaya Bhaskar Annayyolla , Jerin Jacob Kollanukkaran Thread-Topic: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan Thread-Index: AQHVIMtG+KLCgfrjkUKYqOSny9QchKaXc/OzgAALlgCAABCA8g== Date: Wed, 12 Jun 2019 06:38:43 +0000 Message-ID: References: <1559287364-19555-1-git-send-email-thaq@marvell.com> <1560157240-25125-1-git-send-email-thaq@marvell.com>, <8CE3E05A3F976642AAB0F4675D0AD20E0BAB9495@SHSMSX101.ccr.corp.intel.com> , <8CE3E05A3F976642AAB0F4675D0AD20E0BABA5F5@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BABA5F5@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [14.140.231.66] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: b4b6a014-3f13-4196-b4ba-08d6ef009d48 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR18MB3408; x-ms-traffictypediagnostic: MN2PR18MB3408: x-ms-exchange-purlcount: 2 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:7219; x-forefront-prvs: 0066D63CE6 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(376002)(346002)(396003)(39860400002)(366004)(199004)(189003)(13464003)(19627235002)(966005)(107886003)(110136005)(4326008)(54906003)(33656002)(478600001)(99286004)(486006)(6246003)(53946003)(55236004)(25786009)(14454004)(316002)(6116002)(53936002)(2501003)(14444005)(66556008)(66066001)(68736007)(256004)(6306002)(9686003)(3846002)(236005)(54896002)(229853002)(11346002)(19627405001)(102836004)(81156014)(105004)(71200400001)(6436002)(81166006)(53546011)(6506007)(64756008)(8936002)(76176011)(71190400001)(5660300002)(7696005)(446003)(26005)(606006)(76116006)(7736002)(186003)(55016002)(74316002)(30864003)(52536014)(476003)(73956011)(66476007)(2906002)(91956017)(86362001)(66446008)(66946007); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR18MB3408; H:MN2PR18MB2735.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: marvell.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: tb7iKdlcKtsruPIGDvCOfgEPx9Mk4ayhCSi0wzWrXzH13bAEsxwALmD0tD03+Eq3R4WuPKSEYRL21zU8n+IIfdcxFzI9QfqcOw/WR8z1CV9wi/rGowOXiLVMNbYqC3SmflZo2SNWDCBtLdBiwJizZdG4vSi3lCWlxvb9g7eHPoIFsfWhW+yPL2WCwABcwt3YK4ZmUJMRYOtsNeks8wgpmihPHUlGH0eVXjy7kOHkvAfkkfYaZtwMO7tUkJNa5ctV42Jyl1Huxzb8wEgOeo35+iVJoZHoMqOreugXCha2qUC6GVlAeJid9f4uj4lCbod72jX7mAg26XeA6cbMOClQ1zBHrTsFpc9oe515QgVsJSyoZVMXrwgNE9KE1EZIhV1t3X+Cqs/ZNg9MavGygRFmxFr8bk4ZiWZvpS811q5f5nk= Content-Type: multipart/alternative; boundary="_000_MN2PR18MB2735E011D6BDCD607732E19ED4EC0MN2PR18MB2735namp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: b4b6a014-3f13-4196-b4ba-08d6ef009d48 X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jun 2019 06:38:43.6440 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 70e1fb47-1155-421d-87fc-2e58f638b6e0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: thaq@marvell.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR18MB3408 X-OriginatorOrg: marvell.com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-12_04:, , signatures=0 Subject: Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan 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" --_000_MN2PR18MB2735E011D6BDCD607732E19ED4EC0MN2PR18MB2735namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Lijuan, Yes, both are different files. In your previous mail you asked me to submit= the whole test plan, because there is no test_plans/eventdev_pipeline_test= _plan.rst in current DTS. But test_plans/eventdev_pipeline_test_plan.rst is already part of DTS . Regards, - Thanseerul Haq ________________________________ From: Tu, Lijuan Sent: 12 June 2019 11:04 To: Thanseerul Haq; dts@dpdk.org Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukkaran Subject: RE: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance = Testplan Your patch is for test_plans/eventdev_pipeline_perf_test_plan.rst , but the= link you provided is test_plans/eventdev_pipeline_test_plan.rst They are different files, anything I missing? From: Thanseerul Haq [mailto:thaq@marvell.com] Sent: Wednesday, June 12, 2019 1:03 PM To: Tu, Lijuan ; dts@dpdk.org Cc: Faisal Masood ; Vijaya Bhaskar Annayyolla ; Jerin Jacob Kollanukkaran Subject: Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance = Testplan Hi Lijuan, In Current DTS test_plans and scripts are available for eventdev_pipeline f= unctional cases. Test Links: https://git.dpdk.org/tools/dts/tree/test_plans/eventdev_pipeline_test_plan.= rst https://git.dpdk.org/tools/dts/tree/tests/TestSuite_eventdev_pipeline.py Regards, - Thanseerul Haq ________________________________ From: Tu, Lijuan > Sent: 12 June 2019 08:32 To: Thanseerul Haq; dts@dpdk.org Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukkaran Subject: [EXT] RE: [dts] [PATCH v2] Adding Eventdev_pipeline feature perfor= mance Testplan External Email ---------------------------------------------------------------------- Hi thaq, I think you should submit the whole test plan, because there is no test_pla= ns/eventdev_pipeline_test_plan.rst in current DTS. thanks > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com > Sent: Monday, June 10, 2019 5:01 PM > To: dts@dpdk.org > Cc: fmasood@marvell.com; avijay@marvell.com; jerinj@marvell.com; > Thanseerulhaq > > Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance > Testplan > > From: Thanseerulhaq > > > Adding testcase for 1/2/4 NIC ports for eventdev features atomic, paralle= l, > order stages. > > Signed-off-by: Thanseerulhaq > > --- > test_plans/eventdev_pipeline_perf_test_plan.rst | 58 ++++++++++++-------= ---- > -- > 1 file changed, 29 insertions(+), 29 deletions(-) > > diff --git a/test_plans/eventdev_pipeline_perf_test_plan.rst > b/test_plans/eventdev_pipeline_perf_test_plan.rst > index f2b2a7e..619f9a3 100644 > --- a/test_plans/eventdev_pipeline_perf_test_plan.rst > +++ b/test_plans/eventdev_pipeline_perf_test_plan.rst > @@ -30,11 +30,11 @@ echo 24 > /proc/sys/vm/nr_hugepages > > Configure limits of Eventdev devices > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > -Set all eventdev devices sso and ssow limits to zero. Then set eventdev > device under tests sso and ssow limits to non-zero values as per > cores/queues requriments :: > +Set all eventdev devices sso and ssow limits to zero. Then set eventdev > device under tests sso and ssow limits to non-zero values as per > cores/queues requriments :: > echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/sso > echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/ssow > > -Example :: > +Example :: > echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/tim > echo 1 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/npa > echo 16 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/sso > @@ -56,8 +56,8 @@ Description: Execute performance test with Atomic_atq > type of stage in multi-flo > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -D, --dump Print detailed statistics before ex= it > @@ -74,13 +74,13 @@ Description: Execute performance test with > Parallel_atq type of stage in multi-f > > # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_i= d > -w device_bus_id -- -w 0xc00000 -n=3D0 -p --dump > > - Parameters: > + Parameters: > -c, COREMASK : Hexadecimal bitmask of cores to run on > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -p, --parallel : Use parallel scheduling > @@ -97,14 +97,14 @@ Description: Execute performance test with > Ordered_atq type of stage in multi-fl 1. Run the sample with below > command:: > > # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_i= d > -w device_bus_id -- -w 0xc00000 -n=3D0 -o --dump > - > - Parameters: > + > + Parameters: > -c, COREMASK : Hexadecimal bitmask of cores to run on > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -o, --ordered Use ordered scheduling > @@ -127,8 +127,8 @@ Description: Execute performance test with > Atomic_atq type of stage in multi-flo > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -D, --dump Print detailed statistics before ex= it > @@ -145,13 +145,13 @@ Description: Execute performance test with > Parallel_atq type of stage in multi-f > > # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_i= d > -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=3D0 -p --dump > > - Parameters: > + Parameters: > -c, COREMASK : Hexadecimal bitmask of cores to run on > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -p, --parallel : Use parallel scheduling > @@ -168,14 +168,14 @@ Description: Execute performance test with > Ordered_atq type of stage in multi-fl 1. Run the sample with below > command:: > > # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_i= d > -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=3D0 -o --dump > - > - Parameters: > + > + Parameters: > -c, COREMASK : Hexadecimal bitmask of cores to run on > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -o, --ordered Use ordered scheduling > @@ -198,8 +198,8 @@ Description: Execute performance test with > Atomic_atq type of stage in multi-flo > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -D, --dump Print detailed statistics before ex= it > @@ -216,13 +216,13 @@ Description: Execute performance test with > Parallel_atq type of stage in multi-f > > # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_i= d > -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id - > - -w 0xc00000 -n=3D0 -p --dump > > - Parameters: > + Parameters: > -c, COREMASK : Hexadecimal bitmask of cores to run on > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -p, --parallel : Use parallel scheduling > @@ -239,14 +239,14 @@ Description: Execute performance test with > Ordered_atq type of stage in multi-fl 1. Run the sample with below > command:: > > # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_i= d > -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id - > - -w 0xc00000 -n=3D0 -o --dump > - > - Parameters: > + > + Parameters: > -c, COREMASK : Hexadecimal bitmask of cores to run on > -w, --pci-whitelist : Add a PCI device in white list. > Only use the specified PCI devices. The a= rgument format > is <[domain:]bus:devid.func>. This option= can be present > - several times (once per device). > - EAL Commands > + several times (once per device). > + EAL Commands > -w, --worker-mask=3Dcore mask : Run worker on CPUs in core mask > -n, --packets=3DN : Send N packets (default ~32M), 0= implies no > limit > -o, --ordered Use ordered scheduling > -- > 1.8.3.1 --_000_MN2PR18MB2735E011D6BDCD607732E19ED4EC0MN2PR18MB2735namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi Lijuan,

Yes, both are different files. In your previous mail you asked me to submit the whole test plan, because there is= no test_plans/eventdev_pipeline_test_plan.rst in current DTS= .
But test_plans/even= tdev_pipeline_test_plan.rst is already part of DTS .

Regards,

 - Thanseerul Haq

From: Tu, Lijuan <lijuan= .tu@intel.com>
Sent: 12 June 2019 11:04
To: Thanseerul Haq; dts@dpdk.org
Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukka= ran
Subject: RE: [dts] [PATCH v2] Adding Eventdev_pipeline feature perfo= rmance Testplan
 

Your patch is for= test_plans/eventdev_pipeline_perf_test_plan.rst , but the link you provide= d is test_plans/eventdev_pipeline_test_plan.rst

 

They are differen= t files, anything I missing?

&nb= sp;

From: Thanseerul Haq [mailto:thaq@marvell.com]
Sent: Wednesday, June 12, 2019 1:03 PM
To: Tu, Lijuan <lijuan.tu@intel.com>; dts@dpdk.org
Cc: Faisal Masood <fmasood@marvell.com>; Vijaya Bhaskar Annayy= olla <avijay@marvell.com>; Jerin Jacob Kollanukkaran <jerinj@marve= ll.com>
Subject: Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature perfo= rmance Testplan

 

Hi Lijuan,

 

In Current DTS test_plans and scrip= ts are available for eventdev_pipeline functional cases.

 

Test Links:

=  

Regards,

 - Thanseerul Haq

From: = Tu, Lijuan <lijuan.tu@intel.com>
Sent: 12 June 2019 08:32
To: Thanseerul Haq; dts@dpdk.org=
Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukka= ran
Subject: [EXT] RE: [dts] [PATCH v2] Adding Eventdev_pipeline feature= performance Testplan

 

External Email

----------------------------------------------------------------------
Hi thaq,
I think you should submit the whole test plan, because there is no test_pla= ns/eventdev_pipeline_test_plan.rst in current DTS.
thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@= dpdk.org] On Behalf Of thaq@marvell.com
> Sent: Monday, June 10, 2019 5:01 PM
> To: dts@dpdk.org
> Cc: fmasood@marvell.com; avijay@marvell.com; jerinj@marvel= l.com;
> Thanseerulhaq <thaq@marvell.com= >
> Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance=
> Testplan
>
> From: Thanseerulhaq <thaq@marve= ll.com>
>
> Adding testcase for 1/2/4 NIC ports for eventdev features atomic, para= llel,
> order stages.
>
> Signed-off-by: Thanseerulhaq <t= haq@marvell.com>
> ---
>  test_plans/eventdev_pipeline_perf_test_plan.rst | 58 ++&= #43;+++++++++-----------
> --
>  1 file changed, 29 insertions(+), 29 deletions(-)
>
> diff --git a/test_plans/eventdev_pipeline_perf_test_plan.rst
> b/test_plans/eventdev_pipeline_perf_test_plan.rst
> index f2b2a7e..619f9a3 100644
> --- a/test_plans/eventdev_pipeline_perf_test_plan.rst
> +++ b/test_plans/eventdev_pipeline_perf_test_plan.rst
> @@ -30,11 +30,11 @@ echo 24 > /proc/sys/vm/nr_hugepages
>
>  Configure limits of Eventdev devices
>  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> -Set all eventdev devices sso and ssow limits to zero. Then set eventd= ev
> device under tests sso and ssow limits to non-zero values as per
> cores/queues requriments ::
> +Set all eventdev devices sso and ssow limits to zero. Then set ev= entdev
> device under tests sso and ssow limits to non-zero values as per
> cores/queues requriments ::
>     echo 0 > /sys/bus/pci/devices/eventdev_devi= ce_bus_id/limits/sso
>     echo 0 > /sys/bus/pci/devices/eventdev_devi= ce_bus_id/limits/ssow
>
> -Example ::
> +Example ::
>     echo 0 > /sys/bus/pci/devices/eventdev_devi= ce_bus_id/limits/tim
>     echo 1 > /sys/bus/pci/devices/eventdev_devi= ce_bus_id/limits/npa
>     echo 16 > /sys/bus/pci/devices/eventdev_dev= ice_bus_id/limits/sso
> @@ -56,8 +56,8 @@ Description: Execute performance test with Atomi= c_atq
> type of stage in multi-flo
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -D, --dump =             &nb= sp;     Print detailed statistics before exit
> @@ -74,13 +74,13 @@ Description: Execute performance test with
> Parallel_atq type of stage in multi-f
>
>     # ./build/dpdk-eventdev_pipeline -c 0xe00000 -= w eventdev_device_bus_id
> -w device_bus_id -- -w 0xc00000 -n=3D0 -p --dump
>
> -    Parameters:
> +    Parameters:
>          -c, COREMASK&nbs= p;        : Hexadecimal bitmask of cores= to run on
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -p, --parallel&n= bsp;            = ; : Use parallel scheduling
> @@ -97,14 +97,14 @@ Description: Execute performance test with
> Ordered_atq type of stage in multi-fl  1. Run the sample with bel= ow
> command::
>
>     # ./build/dpdk-eventdev_pipeline -c 0xe00000 -= w eventdev_device_bus_id
> -w device_bus_id -- -w 0xc00000 -n=3D0 -o --dump
> -
> -    Parameters:
> +
> +    Parameters:
>          -c, COREMASK&nbs= p;        : Hexadecimal bitmask of cores= to run on
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -o, --ordered&nb= sp;            =    Use ordered scheduling
> @@ -127,8 +127,8 @@ Description: Execute performance test with
> Atomic_atq type of stage in multi-flo
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -D, --dump =             &nb= sp;     Print detailed statistics before exit
> @@ -145,13 +145,13 @@ Description: Execute performance test with > Parallel_atq type of stage in multi-f
>
>     # ./build/dpdk-eventdev_pipeline -c 0xe00000 -= w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=3D0 -p --dump >
> -    Parameters:
> +    Parameters:
>          -c, COREMASK&nbs= p;        : Hexadecimal bitmask of cores= to run on
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -p, --parallel&n= bsp;            = ; : Use parallel scheduling
> @@ -168,14 +168,14 @@ Description: Execute performance test with > Ordered_atq type of stage in multi-fl  1. Run the sample with bel= ow
> command::
>
>     # ./build/dpdk-eventdev_pipeline -c 0xe00000 -= w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=3D0 -o --dump > -
> -    Parameters:
> +
> +    Parameters:
>          -c, COREMASK&nbs= p;        : Hexadecimal bitmask of cores= to run on
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -o, --ordered&nb= sp;            =    Use ordered scheduling
> @@ -198,8 +198,8 @@ Description: Execute performance test with
> Atomic_atq type of stage in multi-flo
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -D, --dump =             &nb= sp;     Print detailed statistics before exit
> @@ -216,13 +216,13 @@ Description: Execute performance test with > Parallel_atq type of stage in multi-f
>
>     # ./build/dpdk-eventdev_pipeline -c 0xe00000 -= w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_i= d -
> - -w 0xc00000 -n=3D0 -p --dump
>
> -    Parameters:
> +    Parameters:
>          -c, COREMASK&nbs= p;        : Hexadecimal bitmask of cores= to run on
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -p, --parallel&n= bsp;            = ; : Use parallel scheduling
> @@ -239,14 +239,14 @@ Description: Execute performance test with > Ordered_atq type of stage in multi-fl  1. Run the sample with bel= ow
> command::
>
>     # ./build/dpdk-eventdev_pipeline -c 0xe00000 -= w eventdev_device_bus_id
> -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_i= d -
> - -w 0xc00000 -n=3D0 -o --dump
> -
> -    Parameters:
> +
> +    Parameters:
>          -c, COREMASK&nbs= p;        : Hexadecimal bitmask of cores= to run on
>          -w, --pci-whitel= ist  : Add a PCI device in white list.
>            = ;            &n= bsp;        Only use the specified PCI d= evices. The argument format
>            = ;            &n= bsp;        is <[domain:]bus:devid.fu= nc>. This option can be present
> -           &nb= sp;            =        several times (once per device).
> -        EAL Commands
> +           = ;            &n= bsp;       several times (once per device). > +        EAL Commands
>          -w, --worker-mas= k=3Dcore mask : Run worker on CPUs in core mask
>          -n, --packets=3D= N             := Send N packets (default ~32M), 0 implies no
> limit
>          -o, --ordered&nb= sp;            =    Use ordered scheduling
> --
> 1.8.3.1

--_000_MN2PR18MB2735E011D6BDCD607732E19ED4EC0MN2PR18MB2735namp_--