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 feature performance Testplan
Date: Mon, 10 Jun 2019 14:27:52 +0530 [thread overview]
Message-ID: <1560157072-24808-1-git-send-email-thaq@marvell.com> (raw)
In-Reply-To: <1559285615-15090-1-git-send-email-thaq@marvell.com>
From: Thanseerulhaq <thaq@marvell.com>
test_plans/eventdev_perf_test_plan.rst: 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_perf_test_plan.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/test_plans/eventdev_perf_test_plan.rst b/test_plans/eventdev_perf_test_plan.rst
index ed1312a..cfe19ef 100644
--- a/test_plans/eventdev_perf_test_plan.rst
+++ b/test_plans/eventdev_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
@@ -58,7 +58,7 @@ 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).
+ several times (once per device).
--prod_type_ethdev : use ethernet device as producer.
--nb_pkts : number of packets to produce, 0 implies no limit
--test : name of the test application to run
@@ -100,7 +100,7 @@ Description: Execute performance test with Atomic_queue type of stage in multi-f
1. Run the sample with below command::
# ./build/dpdk-test-eventdev -l 22-23 -w eventdev_device_bus_id -w device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
-
+
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.
@@ -172,7 +172,7 @@ Description: Execute performance test with Atomic_queue type of stage in multi-f
1. Run the sample with below command::
# ./build/dpdk-test-eventdev -l 22-23 -w eventdev_device_bus_id -w device0_bus_id -w device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
-
+
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.
@@ -245,7 +245,7 @@ Description: Execute performance test with Atomic_queue type of stage in multi-f
1. Run the sample with below command::
# ./build/dpdk-test-eventdev -l 22-23 -w eventdev_device_bus_id -w device0_bus_id -w device1_bus_id -w device2_bus_id -w device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
-
+
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
next prev parent reply other threads:[~2019-06-10 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 6:53 [dts] [PATCH] eventdev_perf_test_plan.rst: " thaq
2019-06-05 2:33 ` Tu, Lijuan
2019-06-10 8:57 ` thaq [this message]
2019-06-12 2:59 ` [dts] [PATCH v2] " 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=1560157072-24808-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).