From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lijuan.tu@intel.com, zhaoyan.chen@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V1 0/1] tests/l2fwd: wait l2fwd boot up ready
Date: Thu, 5 Sep 2019 11:26:30 +0800 [thread overview]
Message-ID: <20190905032631.11298-1-yufengx.mo@intel.com> (raw)
fix l2fwd 'Effective bandwidth is zero' issue when run trex. l2fwd doesn't offer link up query,
here wait 5 second after l2fwd boot up. It is aimed to make sure trex detect link up status.
yufengmx (1):
tests/l2fwd: wait l2fwd boot up ready
tests/TestSuite_l2fwd.py | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.21.0
next reply other threads:[~2019-09-05 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 3:26 yufengmx [this message]
2019-09-05 3:26 ` [dts] [PATCH V1 1/1] " yufengmx
2019-09-05 3:26 ` Mo, YufengX
2019-09-18 6:36 ` Tu, Lijuan
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=20190905032631.11298-1-yufengx.mo@intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=zhaoyan.chen@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).