From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V1][next]tests/nic_single_core_perf: update pktgen input parameter
Date: Thu, 8 Aug 2019 05:45:25 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAFF622@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1565078464-4870-2-git-send-email-yufengx.mo@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Tuesday, August 6, 2019 4:01 PM
> To: dts@dpdk.org
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V1][next]tests/nic_single_core_perf: update pktgen
> input parameter
>
>
> *. update suite nic_single_core_perf with new pktgen measure_throughput
> input parameter definition.
> *. fix typo.
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> tests/TestSuite_nic_single_core_perf.py | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/TestSuite_nic_single_core_perf.py
> b/tests/TestSuite_nic_single_core_perf.py
> index 5b815f4..ca09c72 100644
> --- a/tests/TestSuite_nic_single_core_perf.py
> +++ b/tests/TestSuite_nic_single_core_perf.py
> @@ -101,7 +101,7 @@ class TestNicSingleCorePerf(TestCase):
> self.expected_throughput = self.get_suite_cfg()[
> 'expected_throughput'][self.nic]
>
> - # initilize throughput attribution
> + # initialize throughput attribution
> # {'$framesize':{"$nb_desc": 'throughput'}
> self.throughput = {}
>
> @@ -182,7 +182,7 @@ class TestNicSingleCorePerf(TestCase):
>
> # measure throughput
> stream_ids = self.prepare_stream(frame_size)
> - traffic_opt = {'delay': self.test_duration}
> + traffic_opt = {'duration': self.test_duration}
> _, packets_received = self.tester.pktgen.measure_throughput(
> stream_ids, traffic_opt)
> throughput = packets_received / 1000000.0 @@ -193,7 +193,7 @@
> class TestNicSingleCorePerf(TestCase):
>
> self.verify(throughput,
> "No traffic detected, please check your configuration")
> - self.logger.info("Trouthput of " +
> + self.logger.info("Throughput of " +
> "framesize: {}, rxd/txd: {} is :{} Mpps".format(
> frame_size, nb_desc, throughput))
>
> --
> 1.9.3
prev parent reply other threads:[~2019-08-08 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 8:01 [dts] [PATCH V1][next]tests/nic_single_core_perf: fix wrong input key usage yufengmx
2019-08-06 8:01 ` [dts] [PATCH V1][next]tests/nic_single_core_perf: update pktgen input parameter yufengmx
2019-08-08 5:45 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BAFF622@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@intel.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).