From: "Liu, Yong" <yong.liu@intel.com>
To: "Lu, PeipeiX" <peipeix.lu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Lu, PeipeiX" <peipeix.lu@intel.com>
Subject: Re: [dts] [PATCH V1] fix rxtx_callbacks failed on i350
Date: Tue, 31 Oct 2017 09:01:09 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62F0C4E4@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1509349766-26073-1-git-send-email-peipeix.lu@intel.com>
Peipei,
There has been slightly sleep in sniff_packets function. If 0.5 second is not enough in your environment, you can add a little more like one second in sniff_packets. I think there's no need to wait five seconds.
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lu,peipei
> Sent: Monday, October 30, 2017 3:49 PM
> To: dts@dpdk.org
> Cc: Lu, PeipeiX <peipeix.lu@intel.com>
> Subject: [dts] [PATCH V1] fix rxtx_callbacks failed on i350
>
> After running sniff packet command,need to add sleeping time.
>
> Signed-off-by: lu,peipei <peipeix.lu@intel.com>
> ---
> tests/TestSuite_rxtx_callbacks.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/TestSuite_rxtx_callbacks.py
> b/tests/TestSuite_rxtx_callbacks.py
> index dd968a4..d652378 100644
> --- a/tests/TestSuite_rxtx_callbacks.py
> +++ b/tests/TestSuite_rxtx_callbacks.py
> @@ -78,6 +78,7 @@ class TestRxtxCallbacks(TestCase):
> self.iface_port1 =
> self.tester.get_interface(self.tester.get_local_port(self.dut_ports[1]))
>
> self.inst_port1 = sniff_packets(self.iface_port1)
> + time.sheep(5)
> self.scapy_send_packet(self.iface_port0)
>
> out_port1 = self.get_tcpdump_package(self.inst_port1)
> --
> 1.9.3
prev parent reply other threads:[~2017-10-31 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 7:49 lu,peipei
2017-10-31 9:01 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E62F0C4E4@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=peipeix.lu@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).