test suite reviews and discussions
 help / color / mirror / Atom feed
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 v3] Adding Eventdev_pipeline feature performance Testscript
Date: Mon, 10 Jun 2019 17:55:29 +0530	[thread overview]
Message-ID: <1560169529-16576-1-git-send-email-thaq@marvell.com> (raw)
In-Reply-To: <1559287890-27187-1-git-send-email-thaq@marvell.com>

From: Thanseerulhaq <thaq@marvell.com>

TestSuite_eventdev_pipeline_perf.py: Adding performance testscripts for 1/2/4 NIC ports for eventdev_pipeline features atomic, parallel, order stages.

Signed-off-by: Thanseerulhaq <thaq@marvell.com>
---
 tests/TestSuite_eventdev_pipeline_perf.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/TestSuite_eventdev_pipeline_perf.py b/tests/TestSuite_eventdev_pipeline_perf.py
index 1c23859..54c8381 100644
--- a/tests/TestSuite_eventdev_pipeline_perf.py
+++ b/tests/TestSuite_eventdev_pipeline_perf.py
@@ -293,6 +293,7 @@ class TestEventdevPipelinePerf(TestCase,IxiaPacketGenerator):
                 payload_size = frame_size - self.headers_size
                 self.tester.scapy_append(
                     'wrpcap("event_test.pcap", [Ether(src="52:00:00:00:00:00")/IP(src="1.2.3.4",dst="1.1.1.1")/TCP()/("X"*%d)])' % (payload_size))
+                self.tester.scapy_execute()
 
                 # run traffic generator
                 _, pps = self.tester.traffic_generator_throughput(tgen_input, rate_percent=100, delay=60)
-- 
1.8.3.1


  parent reply	other threads:[~2019-06-10 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31  7:31 [dts] [PATCH] TestSuite_eventdev_pipeline_perf.py: " thaq
2019-05-31 11:28 ` [dts] [PATCH v2] " thaq
2019-06-10 12:25 ` thaq [this message]
2019-06-12  3:13   ` [dts] [PATCH v3] " 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=1560169529-16576-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).