* [dts] [PATCH] eventdev_pipeline_perf_test_plan.rst: Adding Eventdev_pipeline feature performance Testplan. @ 2019-05-31 7:22 thaq 2019-06-05 2:31 ` Tu, Lijuan 2019-06-10 9:00 ` [dts] [PATCH v2] " thaq 0 siblings, 2 replies; 8+ messages in thread From: thaq @ 2019-05-31 7:22 UTC (permalink / raw) To: dts; +Cc: fmasood, avijay, jerinj, Thanseerulhaq From: Thanseerulhaq <thaq@marvell.com> Adding testcase for 1/2/4 NIC ports for eventdev_pipeline features atomic, parallel, order stages. Signed-off-by: Thanseerulhaq <thaq@marvell.com> --- test_plans/eventdev_pipeline_perf_test_plan.rst | 257 ++++++++++++++++++++++++ 1 file changed, 257 insertions(+) create mode 100644 test_plans/eventdev_pipeline_perf_test_plan.rst diff --git a/test_plans/eventdev_pipeline_perf_test_plan.rst b/test_plans/eventdev_pipeline_perf_test_plan.rst new file mode 100644 index 0000000..f2b2a7e --- /dev/null +++ b/test_plans/eventdev_pipeline_perf_test_plan.rst @@ -0,0 +1,257 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright (C) 2019 Marvell International Ltd. + +============================ +Eventdev Pipeline Perf Tests +============================ + +Prerequisites +============== + +Each of the 10Gb/25Gb/40Gb/100Gb Ethernet* ports of the DUT is directly connected in +full-duplex to a different port of the peer Ixia ports(traffic generator). + +Using TCL commands, the Ixia can be configured to send and receive traffic on a given set of ports. + +If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When +using vfio, use the following commands to load the vfio driver and bind it +to the device under test :: + + modprobe vfio + modprobe vfio-pci + usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id + usertools/dpdk-devbind.py --bind=vfio-pci eventdev_device_bus_id + +Create huge pages +================= +mkdir -p /dev/huge +mount -t hugetlbfs none /dev/huge +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 :: + 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 :: + 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 + echo 32 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/ssow + +- ``eventdev_device_bus_id/limits/sso`` : Max limit `256` +- ``eventdev_device_bus_id/limits/ssow``: Max limit `52` + +Test Case: Performance 1port atomic test +======================================== +Description: Execute performance test with Atomic_atq type of stage in multi-flow situation for various cores. + +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 --dump + + 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 + -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 + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 1port parallel test +========================================== +Description: Execute performance test with Parallel_atq type of stage in multi-flow situation for various cores. + +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 -p --dump + + 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 + -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 + -D, --dump : Print detailed statistics before exit + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 1port ordered test +========================================= +Description: Execute performance test with Ordered_atq type of stage in multi-flow situation for various cores. + +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: + -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 + -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 + -D, --dump : Print detailed statistics before exit + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 2port atomic test +======================================== +Description: Execute performance test with Atomic_atq type of stage in multi-flow situation for various cores. + +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 --dump + + 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 + -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 + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 2port parallel test +========================================== +Description: Execute performance test with Parallel_atq type of stage in multi-flow situation for various cores. + +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 -p --dump + + 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 + -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 + -D, --dump : Print detailed statistics before exit + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 2port ordered test +========================================= +Description: Execute performance test with Ordered_atq type of stage in multi-flow situation for various cores. + +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: + -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 + -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 + -D, --dump : Print detailed statistics before exit + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 4port atomic test +======================================== +Description: Execute performance test with Atomic_atq type of stage in multi-flow situation for various cores. + +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 --dump + + 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 + -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 + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 4port parallel test +========================================== +Description: Execute performance test with Parallel_atq type of stage in multi-flow situation for various cores. + +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 -p --dump + + 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 + -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 + -D, --dump : Print detailed statistics before exit + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. + +Test Case: Performance 4port ordered test +========================================= +Description: Execute performance test with Ordered_atq type of stage in multi-flow situation for various cores. + +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: + -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 + -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 + -D, --dump : Print detailed statistics before exit + +2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple) + +3. Observe the speed of packets received(Rx-rate) on Ixia. -- 1.8.3.1 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dts] [PATCH] eventdev_pipeline_perf_test_plan.rst: Adding Eventdev_pipeline feature performance Testplan. 2019-05-31 7:22 [dts] [PATCH] eventdev_pipeline_perf_test_plan.rst: Adding Eventdev_pipeline feature performance Testplan thaq @ 2019-06-05 2:31 ` Tu, Lijuan 2019-06-10 9:00 ` [dts] [PATCH v2] " thaq 1 sibling, 0 replies; 8+ messages in thread From: Tu, Lijuan @ 2019-06-05 2:31 UTC (permalink / raw) To: thaq, dts; +Cc: fmasood, avijay, jerinj Hi thaq, Some minor issues, could you please fix them? Applying: eventdev_pipeline_perf_test_plan.rst: Adding Eventdev_pipeline feature performance Testplan. .git/rebase-apply/patch:44: trailing whitespace. 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 :: .git/rebase-apply/patch:48: trailing whitespace. Example :: .git/rebase-apply/patch:70: trailing whitespace. several times (once per device). .git/rebase-apply/patch:71: trailing whitespace. EAL Commands .git/rebase-apply/patch:88: trailing whitespace. Parameters: warning: squelched 24 whitespace errors warning: 29 lines add whitespace errors. Thanks Lijuan > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com > Sent: Friday, May 31, 2019 3:23 PM > To: dts@dpdk.org > Cc: fmasood@marvell.com; avijay@marvell.com; jerinj@marvell.com; > Thanseerulhaq <thaq@marvell.com> > Subject: [dts] [PATCH] eventdev_pipeline_perf_test_plan.rst: Adding > Eventdev_pipeline feature performance Testplan. > > From: Thanseerulhaq <thaq@marvell.com> > > Adding testcase for 1/2/4 NIC ports for eventdev_pipeline features atomic, > parallel, order stages. > > Signed-off-by: Thanseerulhaq <thaq@marvell.com> > --- > test_plans/eventdev_pipeline_perf_test_plan.rst | 257 > ++++++++++++++++++++++++ > 1 file changed, 257 insertions(+) > create mode 100644 test_plans/eventdev_pipeline_perf_test_plan.rst > > diff --git a/test_plans/eventdev_pipeline_perf_test_plan.rst > b/test_plans/eventdev_pipeline_perf_test_plan.rst > new file mode 100644 > index 0000000..f2b2a7e > --- /dev/null > +++ b/test_plans/eventdev_pipeline_perf_test_plan.rst > @@ -0,0 +1,257 @@ > +.. SPDX-License-Identifier: BSD-3-Clause > + Copyright (C) 2019 Marvell International Ltd. > + > +============================ > +Eventdev Pipeline Perf Tests > +============================ > + > +Prerequisites > +============== > + > +Each of the 10Gb/25Gb/40Gb/100Gb Ethernet* ports of the DUT is directly > +connected in full-duplex to a different port of the peer Ixia ports(traffic > generator). > + > +Using TCL commands, the Ixia can be configured to send and receive traffic > on a given set of ports. > + > +If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in > +bios.When using vfio, use the following commands to load the vfio > +driver and bind it to the device under test :: > + > + modprobe vfio > + modprobe vfio-pci > + usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id > + usertools/dpdk-devbind.py --bind=vfio-pci eventdev_device_bus_id > + > +Create huge pages > +================= > +mkdir -p /dev/huge > +mount -t hugetlbfs none /dev/huge > +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 :: > + 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 :: > + 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 > + echo 32 > /sys/bus/pci/devices/eventdev_device_bus_id/limits/ssow > + > +- ``eventdev_device_bus_id/limits/sso`` : Max limit `256` > +- ``eventdev_device_bus_id/limits/ssow``: Max limit `52` > + > +Test Case: Performance 1port atomic test > +======================================== > +Description: Execute performance test with Atomic_atq type of stage in > multi-flow situation for various cores. > + > +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 --dump > + > + 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 > + -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 > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 1port parallel test > +========================================== > +Description: Execute performance test with Parallel_atq type of stage in > multi-flow situation for various cores. > + > +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 -p --dump > + > + 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 > + -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 > + -D, --dump : Print detailed statistics before exit > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 1port ordered test > +========================================= > +Description: Execute performance test with Ordered_atq type of stage in > multi-flow situation for various cores. > + > +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: > + -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 > + -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 > + -D, --dump : Print detailed statistics before exit > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 2port atomic test > +======================================== > +Description: Execute performance test with Atomic_atq type of stage in > multi-flow situation for various cores. > + > +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 --dump > + > + 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 > + -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 > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 2port parallel test > +========================================== > +Description: Execute performance test with Parallel_atq type of stage in > multi-flow situation for various cores. > + > +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 -p --dump > + > + 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 > + -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 > + -D, --dump : Print detailed statistics before exit > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 2port ordered test > +========================================= > +Description: Execute performance test with Ordered_atq type of stage in > multi-flow situation for various cores. > + > +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: > + -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 > + -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 > + -D, --dump : Print detailed statistics before exit > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 4port atomic test > +======================================== > +Description: Execute performance test with Atomic_atq type of stage in > multi-flow situation for various cores. > + > +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 --dump > + > + 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 > + -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 > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 4port parallel test > +========================================== > +Description: Execute performance test with Parallel_atq type of stage in > multi-flow situation for various cores. > + > +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 -p --dump > + > + 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 > + -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 > + -D, --dump : Print detailed statistics before exit > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > + > +Test Case: Performance 4port ordered test > +========================================= > +Description: Execute performance test with Ordered_atq type of stage in > multi-flow situation for various cores. > + > +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: > + -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 > + -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 > + -D, --dump : Print detailed statistics before exit > + > +2. Use Ixia to send huge number of packets(with same 5-tuple and > +different 5-tuple) > + > +3. Observe the speed of packets received(Rx-rate) on Ixia. > -- > 1.8.3.1 ^ permalink raw reply [flat|nested] 8+ messages in thread
* [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan 2019-05-31 7:22 [dts] [PATCH] eventdev_pipeline_perf_test_plan.rst: Adding Eventdev_pipeline feature performance Testplan thaq 2019-06-05 2:31 ` Tu, Lijuan @ 2019-06-10 9:00 ` thaq 2019-06-12 3:02 ` Tu, Lijuan 1 sibling, 1 reply; 8+ messages in thread From: thaq @ 2019-06-10 9:00 UTC (permalink / raw) To: dts; +Cc: fmasood, avijay, jerinj, Thanseerulhaq From: Thanseerulhaq <thaq@marvell.com> Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel, order stages. Signed-off-by: Thanseerulhaq <thaq@marvell.com> --- 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan 2019-06-10 9:00 ` [dts] [PATCH v2] " thaq @ 2019-06-12 3:02 ` Tu, Lijuan 2019-06-12 5:02 ` Thanseerul Haq 0 siblings, 1 reply; 8+ messages in thread From: Tu, Lijuan @ 2019-06-12 3:02 UTC (permalink / raw) To: thaq, dts; +Cc: fmasood, avijay, jerinj 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 [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 <thaq@marvell.com> > Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance > Testplan > > From: Thanseerulhaq <thaq@marvell.com> > > Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel, > order stages. > > Signed-off-by: Thanseerulhaq <thaq@marvell.com> > --- > 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan 2019-06-12 3:02 ` Tu, Lijuan @ 2019-06-12 5:02 ` Thanseerul Haq 2019-06-12 5:34 ` Tu, Lijuan 0 siblings, 1 reply; 8+ messages in thread From: Thanseerul Haq @ 2019-06-12 5:02 UTC (permalink / raw) To: Tu, Lijuan, dts Cc: Faisal Masood, Vijaya Bhaskar Annayyolla, Jerin Jacob Kollanukkaran [-- Attachment #1: Type: text/plain, Size: 11553 bytes --] Hi Lijuan, In Current DTS test_plans and scripts are available for eventdev_pipeline functional 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 <lijuan.tu@intel.com> 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 performance Testplan 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 [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 <thaq@marvell.com> > Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance > Testplan > > From: Thanseerulhaq <thaq@marvell.com> > > Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel, > order stages. > > Signed-off-by: Thanseerulhaq <thaq@marvell.com> > --- > 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 [-- Attachment #2: Type: text/html, Size: 25940 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan 2019-06-12 5:02 ` Thanseerul Haq @ 2019-06-12 5:34 ` Tu, Lijuan 2019-06-12 6:38 ` Thanseerul Haq 0 siblings, 1 reply; 8+ messages in thread From: Tu, Lijuan @ 2019-06-12 5:34 UTC (permalink / raw) To: Thanseerul Haq, dts Cc: Faisal Masood, Vijaya Bhaskar Annayyolla, Jerin Jacob Kollanukkaran [-- Attachment #1: Type: text/plain, Size: 12363 bytes --] 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 <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 Hi Lijuan, In Current DTS test_plans and scripts are available for eventdev_pipeline functional 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 <lijuan.tu@intel.com<mailto:lijuan.tu@intel.com>> Sent: 12 June 2019 08:32 To: Thanseerul Haq; dts@dpdk.org<mailto:dts@dpdk.org> Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukkaran 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_plans/eventdev_pipeline_test_plan.rst in current DTS. thanks > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com<mailto:thaq@marvell.com> > Sent: Monday, June 10, 2019 5:01 PM > To: dts@dpdk.org<mailto:dts@dpdk.org> > Cc: fmasood@marvell.com<mailto:fmasood@marvell.com>; avijay@marvell.com<mailto:avijay@marvell.com>; jerinj@marvell.com<mailto:jerinj@marvell.com>; > Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance > Testplan > > From: Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > > Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel, > order stages. > > Signed-off-by: Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > --- > 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 [-- Attachment #2: Type: text/html, Size: 29896 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan 2019-06-12 5:34 ` Tu, Lijuan @ 2019-06-12 6:38 ` Thanseerul Haq 2019-06-12 7:03 ` Tu, Lijuan 0 siblings, 1 reply; 8+ messages in thread From: Thanseerul Haq @ 2019-06-12 6:38 UTC (permalink / raw) To: Tu, Lijuan, dts Cc: Faisal Masood, Vijaya Bhaskar Annayyolla, Jerin Jacob Kollanukkaran [-- Attachment #1: Type: text/plain, Size: 12990 bytes --] 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 <lijuan.tu@intel.com> 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 <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 Hi Lijuan, In Current DTS test_plans and scripts are available for eventdev_pipeline functional 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 <lijuan.tu@intel.com<mailto:lijuan.tu@intel.com>> Sent: 12 June 2019 08:32 To: Thanseerul Haq; dts@dpdk.org<mailto:dts@dpdk.org> Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukkaran 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_plans/eventdev_pipeline_test_plan.rst in current DTS. thanks > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com<mailto:thaq@marvell.com> > Sent: Monday, June 10, 2019 5:01 PM > To: dts@dpdk.org<mailto:dts@dpdk.org> > Cc: fmasood@marvell.com<mailto:fmasood@marvell.com>; avijay@marvell.com<mailto:avijay@marvell.com>; jerinj@marvell.com<mailto:jerinj@marvell.com>; > Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance > Testplan > > From: Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > > Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel, > order stages. > > Signed-off-by: Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > --- > 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 [-- Attachment #2: Type: text/html, Size: 30814 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance Testplan 2019-06-12 6:38 ` Thanseerul Haq @ 2019-06-12 7:03 ` Tu, Lijuan 0 siblings, 0 replies; 8+ messages in thread From: Tu, Lijuan @ 2019-06-12 7:03 UTC (permalink / raw) To: Thanseerul Haq, dts Cc: Faisal Masood, Vijaya Bhaskar Annayyolla, Jerin Jacob Kollanukkaran [-- Attachment #1: Type: text/plain, Size: 13703 bytes --] Sorry, I make a mistake, could you submit V2 of the whole file "test_plans/eventdev_pipeline_perf_test_plan.rst", because v1 got some warning, and I didn't merge them. From: Thanseerul Haq [mailto:thaq@marvell.com] Sent: Wednesday, June 12, 2019 2:39 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 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 <lijuan.tu@intel.com<mailto:lijuan.tu@intel.com>> Sent: 12 June 2019 11:04 To: Thanseerul Haq; dts@dpdk.org<mailto: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 <lijuan.tu@intel.com<mailto:lijuan.tu@intel.com>>; dts@dpdk.org<mailto:dts@dpdk.org> Cc: Faisal Masood <fmasood@marvell.com<mailto:fmasood@marvell.com>>; Vijaya Bhaskar Annayyolla <avijay@marvell.com<mailto:avijay@marvell.com>>; Jerin Jacob Kollanukkaran <jerinj@marvell.com<mailto:jerinj@marvell.com>> 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 functional 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 <lijuan.tu@intel.com<mailto:lijuan.tu@intel.com>> Sent: 12 June 2019 08:32 To: Thanseerul Haq; dts@dpdk.org<mailto:dts@dpdk.org> Cc: Faisal Masood; Vijaya Bhaskar Annayyolla; Jerin Jacob Kollanukkaran 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_plans/eventdev_pipeline_test_plan.rst in current DTS. thanks > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com<mailto:thaq@marvell.com> > Sent: Monday, June 10, 2019 5:01 PM > To: dts@dpdk.org<mailto:dts@dpdk.org> > Cc: fmasood@marvell.com<mailto:fmasood@marvell.com>; avijay@marvell.com<mailto:avijay@marvell.com>; jerinj@marvell.com<mailto:jerinj@marvell.com>; > Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > Subject: [dts] [PATCH v2] Adding Eventdev_pipeline feature performance > Testplan > > From: Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > > Adding testcase for 1/2/4 NIC ports for eventdev features atomic, parallel, > order stages. > > Signed-off-by: Thanseerulhaq <thaq@marvell.com<mailto:thaq@marvell.com>> > --- > 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 [-- Attachment #2: Type: text/html, Size: 34510 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-06-12 7:03 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-05-31 7:22 [dts] [PATCH] eventdev_pipeline_perf_test_plan.rst: Adding Eventdev_pipeline feature performance Testplan thaq 2019-06-05 2:31 ` Tu, Lijuan 2019-06-10 9:00 ` [dts] [PATCH v2] " thaq 2019-06-12 3:02 ` Tu, Lijuan 2019-06-12 5:02 ` Thanseerul Haq 2019-06-12 5:34 ` Tu, Lijuan 2019-06-12 6:38 ` Thanseerul Haq 2019-06-12 7:03 ` Tu, Lijuan
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).