From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dts] [PATCH V1 1/1] tests/l2fwd: wait l2fwd boot up ready
Date: Wed, 18 Sep 2019 06:36:40 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB23BCD@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190905032631.11298-2-yufengx.mo@intel.com>
Applied, thanks
> -----Original Message-----
> From: Mo, YufengX
> Sent: Thursday, September 5, 2019 11:27 AM
> To: dts@dpdk.org; Tu, Lijuan <lijuan.tu@intel.com>; Chen, Zhaoyan
> <zhaoyan.chen@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts][PATCH V1 1/1] tests/l2fwd: wait l2fwd boot up ready
>
>
> wait 5 second after l2fwd boot up. It is aimed to make sure trex detect link
> up status.
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> tests/TestSuite_l2fwd.py | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_l2fwd.py b/tests/TestSuite_l2fwd.py index
> e2c4118..ace5dff 100644
> --- a/tests/TestSuite_l2fwd.py
> +++ b/tests/TestSuite_l2fwd.py
> @@ -196,7 +196,10 @@ class TestL2fwd(TestCase):
>
> # self.dut.send_expect(command_line, "memory mapped", 60)
> self.dut.send_expect(command_line, "L2FWD: entering main loop",
> 60)
> -
> + # wait 5 second after l2fwd boot up.
> + # It is aimed to make sure trex detect link up status.
> + if self.tester.is_pktgen:
> + time.sleep(5)
> info = "Executing l2fwd using %s queues, frame size %d and %s
> setup.\n" % \
> (queues['queues'], frame_size, self.core_config)
>
> --
> 2.21.0
prev parent reply other threads:[~2019-09-18 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 3:26 [dts] [PATCH V1 0/1] " yufengmx
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 [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=8CE3E05A3F976642AAB0F4675D0AD20E0BB23BCD@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@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).