From: <thaq@marvell.com>
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
Date: Mon, 10 Jun 2019 14:30:40 +0530 [thread overview]
Message-ID: <1560157240-25125-1-git-send-email-thaq@marvell.com> (raw)
In-Reply-To: <1559287364-19555-1-git-send-email-thaq@marvell.com>
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
next prev parent reply other threads:[~2019-06-10 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 7:22 [dts] [PATCH] eventdev_pipeline_perf_test_plan.rst: " thaq
2019-06-05 2:31 ` Tu, Lijuan
2019-06-10 9:00 ` thaq [this message]
2019-06-12 3:02 ` [dts] [PATCH v2] " 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1560157240-25125-1-git-send-email-thaq@marvell.com \
--to=thaq@marvell.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=jerinj@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).