<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> 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<o:p></o:p> <o:p> </o:p> They are different files, anything I missing? <o:p></o:p> <a name="_MailEndCompose"><o:p> </o:p></a> <div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> <a name="_____replyseparator"></a>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 Annayyolla <avijay@marvell.com>; Jerin Jacob Kollanukkaran <jerinj@marvell.com> Subject: Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan<o:p></o:p> </div> </div> <o:p> </o:p> <div> Hi Lijuan,<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> In Current DTS test_plans and scripts are available for eventdev_pipeline functional cases.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Test Links:<o:p></o:p> </div> <div> <a href="https://git.dpdk.org/tools/dts/tree/test_plans/eventdev_pipeline_test_plan.rst" id="LPlnk808148">https://git.dpdk.org/tools/dts/tree/test_plans/eventdev_pipeline_test_plan.rst</a> <o:p></o:p> </div> <div> <a href="https://git.dpdk.org/tools/dts/tree/tests/TestSuite_eventdev_pipeline.py" id="LPlnk364345">https://git.dpdk.org/tools/dts/tree/tests/TestSuite_eventdev_pipeline.py</a><o:p></o:p> </div> <div id="Signature"> <div id="divtagdefaultwrapper"> <o:p> </o:p> Regards,<o:p></o:p> - Thanseerul Haq<o:p></o:p> </div> </div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="3" width="98%" align="center"> </div> <div id="divRplyFwdMsg"> From: Tu, Lijuan <<a href="mailto:lijuan.tu@intel.com">lijuan.tu@intel.com</a>> Sent: 12 June 2019 08:32 To: Thanseerul Haq; <a href="mailto:dts@dpdk.org">dts@dpdk.org</a> Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukkaran Subject: [EXT] RE: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan <o:p></o:p> <div> <o:p></o:p> </div> </div> <div> <div> External Email ---------------------------------------------------------------------- Hi thaq, I think you should submit the whole test plan, because there is no test_plans/eventdev_pipeline_test_plan.rst in current DTS. thanks > -----Original Message----- > From: dts [<a href="mailto:dts-bounces@dpdk.org">mailto:dts-bounces@dpdk.org</a>] On Behalf Of <a href="mailto:thaq@marvell.com">thaq@marvell.com</a> > Sent: Monday, June 10, 2019 5:01 PM > To: <a href="mailto:dts@dpdk.org">dts@dpdk.org</a> > Cc: <a href="mailto:fmasood@marvell.com">fmasood@marvell.com</a>; <a href="mailto:avijay@marvell.com"> avijay@marvell.com</a>; <a href="mailto:jerinj@marvell.com">jerinj@marvell.com</a>; > Thanseerulhaq <<a href="mailto:thaq@marvell.com">thaq@marvell.com</a>> > Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance > Testplan > > From: Thanseerulhaq <<a href="mailto:thaq@marvell.com">thaq@marvell.com</a>> > > Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel, > order stages. > > Signed-off-by: Thanseerulhaq <<a href="mailto:thaq@marvell.com">thaq@marvell.com</a>> > --- > 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 > ==================================== > -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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : Send N packets (default ~32M), 0 implies no > limit > -D, --dump 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=0 -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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : 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_id > -w device_bus_id -- -w 0xc00000 -n=0 -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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : 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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : Send N packets (default ~32M), 0 implies no > limit > -D, --dump 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=0 -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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : 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_id > -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=0 -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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : 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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : Send N packets (default ~32M), 0 implies no > limit > -D, --dump 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_id - > - -w 0xc00000 -n=0 -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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : 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_id > -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id - > - -w 0xc00000 -n=0 -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 argument 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=core mask : Run worker on CPUs in core mask > -n, --packets=N : Send N packets (default ~32M), 0 implies no > limit > -o, --ordered Use ordered scheduling > -- > 1.8.3.1<o:p></o:p> </div> </div> </div> </div> </body> </html>