From: "Wang, FeiX Y" <feix.y.wang@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [Patch V1] framework/tester.py : add this function to support ixia to send fixed number of packets during certain period it is only for test_suite nic_single_core_perf, not for common use
Date: Fri, 22 Sep 2017 05:59:38 +0000 [thread overview]
Message-ID: <A527267237D7C74DAC8B4819E4DDAD2302D09F00@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E62EC98E9@SHSMSX103.ccr.corp.intel.com>
Hi, Yong
Yes ,that's right, the value " runtime" is only to make sure all the packets configured to be transmitted out within the period.
Ok, then I will add a check to see if the actual transmitted packets is as configured.
Thanks
fei
-----Original Message-----
From: Liu, Yong
Sent: Friday, September 22, 2017 1:51 PM
To: Wang, FeiX Y <feix.y.wang@intel.com>; dts@dpdk.org
Cc: Wang, FeiX Y <feix.y.wang@intel.com>
Subject: RE: [dts] [Patch V1] framework/tester.py : add this function to support ixia to send fixed number of packets during certain period it is only for test_suite nic_single_core_perf, not for common use
Fei,
Please make sure your code align to pep style.
I still has question for parameter "runTime", this value is depend on rate, total number and link rate.
I think the only value for this parameter is to make sure all packets transmitted.
Why not just check how many packets emitted and return when equal to parameter "packetNum".
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of wang fei
> Sent: Wednesday, September 20, 2017 8:31 PM
> To: dts@dpdk.org
> Cc: Wang, FeiX Y <feix.y.wang@intel.com>
> Subject: [dts] [Patch V1] framework/tester.py : add this function to
> support ixia to send fixed number of packets during certain period it
> is only for test_suite nic_single_core_perf, not for common use
>
> Signed-off-by: wang fei <feix.y.wang@intel.com>
> ---
> framework/tester.py | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/framework/tester.py b/framework/tester.py index
> e7fb6bc..78202d0 100644
> --- a/framework/tester.py
> +++ b/framework/tester.py
> @@ -491,6 +491,17 @@ class Tester(Crb):
>
> return out.rpartition('[')[0]
>
> + def
> traffic_generator_send_packets(self,portList,ratePercent,packetNum,del
> ay=5
> ,runTime=60):
> + """
> + send fixed number of packets on specified ports during
> + runTime
> time.
> + Be note that this function is only used for
> + nic_single_core_perf
> test case, not for common use
> + """
> + if self.check_port_list(portList, 'ixia'):
> + return self.ixia_packet_gen.send_packets(portList,
> ratePercent, packetNum,delay,runTime)
> + if not self.check_port_list(portList):
> + self.logger.warning("exception by mixed port types")
> + return None
> +
> def traffic_generator_throughput(self, portList,
> rate_percent=100,
> delay=5):
> """
> Run throughput performance test on specified ports.
> --
> 2.7.4
prev parent reply other threads:[~2017-09-22 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 12:31 wang fei
2017-09-22 5:51 ` Liu, Yong
2017-09-22 5:59 ` Wang, FeiX Y [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=A527267237D7C74DAC8B4819E4DDAD2302D09F00@shsmsx102.ccr.corp.intel.com \
--to=feix.y.wang@intel.com \
--cc=dts@dpdk.org \
--cc=yong.liu@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).