From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "thaq@marvell.com" <thaq@marvell.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "fmasood@marvell.com" <fmasood@marvell.com>,
"avijay@marvell.com" <avijay@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>
Subject: Re: [dts] [PATCH v3] Adding Eventdev_pipeline feature performance Testscript
Date: Wed, 12 Jun 2019 03:13:58 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAB94E1@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1560169529-16576-1-git-send-email-thaq@marvell.com>
Just to clarify DTS work mode:
1, I will apply test plan firstly, then apply test script. Test script will be considered until teat plan merged.
2, I will deal with patch weekly, usually on Wednesday at PRC time.
3, If the patch are not applied, and you want to change something, you could sent V2, V3, if you patch based on your own patch which not applied, will cause failure.
According to above, so this patch can't be merged because of applying failure.
Thanks
Lijuan
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com
> Sent: Monday, June 10, 2019 8:25 PM
> 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
>
> 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
prev parent reply other threads:[~2019-06-12 3:14 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 ` [dts] [PATCH v3] " thaq
2019-06-12 3:13 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BAB94E1@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=jerinj@marvell.com \
--cc=thaq@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).