From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1] tests/unit_test_loopback: add '-j' option to 'make'
Date: Wed, 3 Jul 2019 05:52:46 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAD9297@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1561998570-8839-1-git-send-email-wenjiex.a.li@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Tuesday, July 2, 2019 12:30 AM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V1] tests/unit_test_loopback: add '-j' option to 'make'
>
> "make" takes more time, sometimes it is over 120 seconds.
> Using "make -j" could save time.
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> tests/TestSuite_unit_tests_loopback.py | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/TestSuite_unit_tests_loopback.py
> b/tests/TestSuite_unit_tests_loopback.py
> index ad49e8a..50533a6 100644
> --- a/tests/TestSuite_unit_tests_loopback.py
> +++ b/tests/TestSuite_unit_tests_loopback.py
> @@ -92,7 +92,7 @@ class TestUnitTestsLoopback(TestCase):
> """
> self.dut.send_expect("sed -i -e 's/lpbk_mode = 0/lpbk_mode = 1/'
> app/test/test_pmd_perf.c", "# ", 30)
> self.dut.send_expect("cd app/test", "# ")
> - self.dut.send_expect("make", "# ", 120)
> + self.dut.send_expect("make -j", "# ", 120)
> self.dut.send_expect("cd /root/dpdk", "# ")
>
> self.tester.send_expect("rm -rf ./getPackageByTcpdump.cap", "#") @@ -
> 113,7 +113,7 @@ class TestUnitTestsLoopback(TestCase):
> """
> self.dut.send_expect("sed -i -e 's/lpbk_mode = 1/lpbk_mode = 0/'
> app/test/test_pmd_perf.c", "# ", 30)
> self.dut.send_expect("cd app/test", "# ")
> - self.dut.send_expect("make", "# ", 120)
> + self.dut.send_expect("make -j", "# ", 120)
> self.dut.send_expect("cd /root/dpdk", "# ")
>
> self.tester.send_expect("rm -rf ./getPackageByTcpdump.cap", "#") @@ -
> 140,6 +140,6 @@ class TestUnitTestsLoopback(TestCase):
> self.dut.send_expect("sed -i -e 's/lpbk_mode = 0/lpbk_mode = 1/'
> app/test/test_pmd_perf.c", "# ", 30)
> self.dut.send_expect("sed -i -e 's/#define MAX_TRAFFIC_BURST
> 32/#define MAX_TRAFFIC_BURST %s/' app/test/test_pmd_perf.c" %
> self.max_traffic_burst, "# ", 30)
> self.dut.send_expect("cd app/test", "# ")
> - self.dut.send_expect("make", "# ", 120)
> + self.dut.send_expect("make -j", "# ", 120)
> self.dut.send_expect("cd /root/dpdk", "# ")
> self.dut.kill_all()
> --
> 2.17.1
prev parent reply other threads:[~2019-07-03 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 16:29 Wenjie Li
2019-07-03 5:52 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BAD9297@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=wenjiex.a.li@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).