From: "lu,peipei" <peipeix.lu@intel.com>
To: dts@dpdk.org
Cc: "lu,peipei" <peipeix.lu@intel.com>
Subject: [dts] [PATCH V1] framework/packet: fix netmap_compat and rxtx_callbacksfailed on i350 and sagepond
Date: Tue, 30 Jan 2018 15:14:23 +0800 [thread overview]
Message-ID: <1517296463-35565-1-git-send-email-peipeix.lu@intel.com> (raw)
i350 and sagepond need additional timeout about netmap_compat and
rxtx_callbacksfailed cases
Signed-off-by: lu,peipei <peipeix.lu@intel.com>
---
framework/packet.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/framework/packet.py b/framework/packet.py
index 908e855..976b82b 100755
--- a/framework/packet.py
+++ b/framework/packet.py
@@ -855,7 +855,7 @@ def sniff_packets(intf, count=0, timeout=5, filters=[]):
pipe = subprocess.Popen(args)
index = str(time.time())
SNIFF_PIDS[index] = (pipe, intf, timeout)
- time.sleep(0.5)
+ time.sleep(1)
return index
--
1.9.3
next reply other threads:[~2018-01-30 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 7:14 lu,peipei [this message]
2018-01-30 15:33 ` Liu, Yong
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=1517296463-35565-1-git-send-email-peipeix.lu@intel.com \
--to=peipeix.lu@intel.com \
--cc=dts@dpdk.org \
/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).