<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Hi Lijuan,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<font size="2"><span style="font-size:11pt">In Current DTS test_plans and scripts are available for eventdev_pipeline functional cases.</span></font></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<font size="2"><span style="font-size:11pt"><u><br>
</u></span></font></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<font size="2"><span style="font-size:11pt"><u>Test Links:</u><br>
</span></font></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<font size="2"><span style="font-size:11pt"><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>
</span></font><br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<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><br>
</div>
<div id="Signature">
<div></div>
<div></div>
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top:0px; margin-bottom:0px; margin-top:0; margin-bottom:0"><span style="font-size:11pt; line-height:normal"><br>
</span></p>
<p style="margin-top:0px; margin-bottom:0px; margin-top:0; margin-bottom:0"><span style="font-size:11pt; line-height:normal">Regards,</span></p>
<p style="margin-top:0px; margin-bottom:0px; margin-top:0; margin-bottom:0"><span style="font-size:11pt; line-height:normal"><i style="line-height:normal"> - Thanseerul Haq</i></span></p>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Tu, Lijuan <lijuan.tu@intel.com><br>
<b>Sent:</b> 12 June 2019 08:32<br>
<b>To:</b> Thanseerul Haq; dts@dpdk.org<br>
<b>Cc:</b> Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukkaran<br>
<b>Subject:</b> [EXT] RE: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">External Email<br>
<br>
----------------------------------------------------------------------<br>
Hi thaq,<br>
I think you should submit the whole test plan, because there is no test_plans/eventdev_pipeline_test_plan.rst in current DTS.<br>
thanks<br>
<br>
> -----Original Message-----<br>
> From: dts [<a href="mailto:dts-bounces@dpdk.org">mailto:dts-bounces@dpdk.org</a>] On Behalf Of thaq@marvell.com<br>
> Sent: Monday, June 10, 2019 5:01 PM<br>
> To: dts@dpdk.org<br>
> Cc: fmasood@marvell.com; avijay@marvell.com; jerinj@marvell.com;<br>
> Thanseerulhaq <thaq@marvell.com><br>
> Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance<br>
> Testplan<br>
> <br>
> From: Thanseerulhaq <thaq@marvell.com><br>
> <br>
> Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel,<br>
> order stages.<br>
> <br>
> Signed-off-by: Thanseerulhaq <thaq@marvell.com><br>
> ---<br>
> test_plans/eventdev_pipeline_perf_test_plan.rst | 58 ++++++++++++-----------<br>
> --<br>
> 1 file changed, 29 insertions(+), 29 deletions(-)<br>
> <br>
> diff --git a/test_plans/eventdev_pipeline_perf_test_plan.rst<br>
> b/test_plans/eventdev_pipeline_perf_test_plan.rst<br>
> index f2b2a7e..619f9a3 100644<br>
> --- a/test_plans/eventdev_pipeline_perf_test_plan.rst<br>
> +++ b/test_plans/eventdev_pipeline_perf_test_plan.rst<br>
> @@ -30,11 +30,11 @@ echo 24 > /proc/sys/vm/nr_hugepages<br>
> <br>
> Configure limits of Eventdev devices<br>
> ====================================<br>
> -Set all eventdev devices sso and ssow limits to zero. Then set eventdev<br>
> device under tests sso and ssow limits to non-zero values as per<br>
> cores/queues requriments ::<br>
> +Set all eventdev devices sso and ssow limits to zero. Then set eventdev<br>
> device under tests sso and ssow limits to non-zero values as per<br>
> cores/queues requriments ::<br>
> echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/sso<br>
> echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/ssow<br>
> <br>
> -Example ::<br>
> +Example ::<br>
> echo 0 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/tim<br>
> echo 1 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/npa<br>
> echo 16 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/sso<br>
> @@ -56,8 +56,8 @@ Description: Execute performance test with Atomic_atq<br>
> type of stage in multi-flo<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -D, --dump Print detailed statistics before exit<br>
> @@ -74,13 +74,13 @@ Description: Execute performance test with<br>
> Parallel_atq type of stage in multi-f<br>
> <br>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id<br>
> -w device_bus_id -- -w 0xc00000 -n=0 -p --dump<br>
> <br>
> - Parameters:<br>
> + Parameters:<br>
> -c, COREMASK : Hexadecimal bitmask of cores to run on<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -p, --parallel : Use parallel scheduling<br>
> @@ -97,14 +97,14 @@ Description: Execute performance test with<br>
> Ordered_atq type of stage in multi-fl 1. Run the sample with below<br>
> command::<br>
> <br>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id<br>
> -w device_bus_id -- -w 0xc00000 -n=0 -o --dump<br>
> -<br>
> - Parameters:<br>
> +<br>
> + Parameters:<br>
> -c, COREMASK : Hexadecimal bitmask of cores to run on<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -o, --ordered Use ordered scheduling<br>
> @@ -127,8 +127,8 @@ Description: Execute performance test with<br>
> Atomic_atq type of stage in multi-flo<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -D, --dump Print detailed statistics before exit<br>
> @@ -145,13 +145,13 @@ Description: Execute performance test with<br>
> Parallel_atq type of stage in multi-f<br>
> <br>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id<br>
> -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=0 -p --dump<br>
> <br>
> - Parameters:<br>
> + Parameters:<br>
> -c, COREMASK : Hexadecimal bitmask of cores to run on<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -p, --parallel : Use parallel scheduling<br>
> @@ -168,14 +168,14 @@ Description: Execute performance test with<br>
> Ordered_atq type of stage in multi-fl 1. Run the sample with below<br>
> command::<br>
> <br>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id<br>
> -w device0_bus_id -w device1_bus_id -- -w 0xc00000 -n=0 -o --dump<br>
> -<br>
> - Parameters:<br>
> +<br>
> + Parameters:<br>
> -c, COREMASK : Hexadecimal bitmask of cores to run on<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -o, --ordered Use ordered scheduling<br>
> @@ -198,8 +198,8 @@ Description: Execute performance test with<br>
> Atomic_atq type of stage in multi-flo<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -D, --dump Print detailed statistics before exit<br>
> @@ -216,13 +216,13 @@ Description: Execute performance test with<br>
> Parallel_atq type of stage in multi-f<br>
> <br>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id<br>
> -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id -<br>
> - -w 0xc00000 -n=0 -p --dump<br>
> <br>
> - Parameters:<br>
> + Parameters:<br>
> -c, COREMASK : Hexadecimal bitmask of cores to run on<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -p, --parallel : Use parallel scheduling<br>
> @@ -239,14 +239,14 @@ Description: Execute performance test with<br>
> Ordered_atq type of stage in multi-fl 1. Run the sample with below<br>
> command::<br>
> <br>
> # ./build/dpdk-eventdev_pipeline -c 0xe00000 -w eventdev_device_bus_id<br>
> -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id -<br>
> - -w 0xc00000 -n=0 -o --dump<br>
> -<br>
> - Parameters:<br>
> +<br>
> + Parameters:<br>
> -c, COREMASK : Hexadecimal bitmask of cores to run on<br>
> -w, --pci-whitelist : Add a PCI device in white list.<br>
> Only use the specified PCI devices. The argument format<br>
> is <[domain:]bus:devid.func>. This option can be present<br>
> - several times (once per device).<br>
> - EAL Commands<br>
> + several times (once per device).<br>
> + EAL Commands<br>
> -w, --worker-mask=core mask : Run worker on CPUs in core mask<br>
> -n, --packets=N : Send N packets (default ~32M), 0 implies no<br>
> limit<br>
> -o, --ordered Use ordered scheduling<br>
> --<br>
> 1.8.3.1<br>
<br>
</div>
</span></font></div>
</body>
</html>