From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiang, YuX" <yux.jiang@intel.com>, "Jiang@dpdk.org" <Jiang@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/virtio_cryptodev: Adapt latest make method to build dpdk
Date: Mon, 20 Jul 2020 07:30:03 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC82361@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200714031912.12206-1-yux.jiang@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Jiang, YuX
> Sent: 2020年7月14日 11:19
> To: dts@dpdk.org
> Cc: Jiang, YuX <yux.jiang@intel.com>; Jiang@dpdk.org
> Subject: [dts] [PATCH V1] tests/virtio_cryptodev: Adapt latest make method to
> build dpdk
>
> From: "Jiang,yu" <yux.jiang@intel.com>
>
> The latest compilation method changes, so adapt latest make method to build
> dpdk.
>
> Signed-off-by: Jiang,yu <yux.jiang@intel.com>
> ---
> tests/TestSuite_virtio_ipsec_cryptodev_func.py | 2 +-
> tests/TestSuite_virtio_perf_cryptodev_func.py | 2 +-
> tests/TestSuite_virtio_unit_cryptodev_func.py | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/TestSuite_virtio_ipsec_cryptodev_func.py
> b/tests/TestSuite_virtio_ipsec_cryptodev_func.py
> index d812e36..8231d0f 100644
> --- a/tests/TestSuite_virtio_ipsec_cryptodev_func.py
> +++ b/tests/TestSuite_virtio_ipsec_cryptodev_func.py
> @@ -98,7 +98,7 @@ class VirtioCryptodevIpsecTest(TestCase):
> "sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_AESNI_MB=n$/CONFIG_RTE_LIBRTE_PMD_AESN
> I_MB=y/' config/common_base", '#', 30)
> user_dut.send_expect(
> "sed -i
> 's/CONFIG_RTE_EAL_IGB_UIO=n/CONFIG_RTE_EAL_IGB_UIO=y/g'
> config/common_base", '#', 30)
> - out = user_dut.send_expect("make install T=%s" % self.target, "# ", 1200)
> + out = user_dut.send_expect("make -j %d install T=%s
> + MAKE_PAUSE=n" % (user_dut.number_of_cores, self.target), "# ", 1200)
> #user_dut.build_install_dpdk(self.target)
> out = user_dut.build_dpdk_apps("./examples/ipsec-secgw")
> self.logger.info(out)
> diff --git a/tests/TestSuite_virtio_perf_cryptodev_func.py
> b/tests/TestSuite_virtio_perf_cryptodev_func.py
> index 830d62d..5323fc6 100644
> --- a/tests/TestSuite_virtio_perf_cryptodev_func.py
> +++ b/tests/TestSuite_virtio_perf_cryptodev_func.py
> @@ -119,7 +119,7 @@ class VirtioCryptodevPerfTest(TestCase):
> "sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_AESNI_MB=n$/CONFIG_RTE_LIBRTE_PMD_AESN
> I_MB=y/' config/common_base", '#', 30)
> user_dut.send_expect(
> "sed -i
> 's/CONFIG_RTE_EAL_IGB_UIO=n/CONFIG_RTE_EAL_IGB_UIO=y/g'
> config/common_base", '#', 30)
> - out = user_dut.send_expect("make install T=%s" % self.target, "# ", 900)
> + out = user_dut.send_expect("make -j %d install T=%s
> + MAKE_PAUSE=n" % (user_dut.number_of_cores, self.target), "# ", 900)
>
> self.verify("Error" not in out, "compilation error 1")
> self.verify("No such file" not in out, "compilation error 2") diff --git
> a/tests/TestSuite_virtio_unit_cryptodev_func.py
> b/tests/TestSuite_virtio_unit_cryptodev_func.py
> index b828d6f..47e9c47 100644
> --- a/tests/TestSuite_virtio_unit_cryptodev_func.py
> +++ b/tests/TestSuite_virtio_unit_cryptodev_func.py
> @@ -91,7 +91,7 @@ class VirtioCryptodevUnitTest(TestCase):
> "sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_AESNI_MB=n$/CONFIG_RTE_LIBRTE_PMD_AESN
> I_MB=y/' config/common_base", '#', 30)
> user_dut.send_expect(
> "sed -i
> 's/CONFIG_RTE_EAL_IGB_UIO=n/CONFIG_RTE_EAL_IGB_UIO=y/g'
> config/common_base", '#', 30)
> - out = user_dut.send_expect("make install T=%s" % self.target, "# ", 900)
> + out = user_dut.send_expect("make -j %d install T=%s
> + MAKE_PAUSE=n" % (user_dut.number_of_cores, self.target), "# ", 900)
> self.verify("Error" not in out, "compilation error 1")
> self.verify("No such file" not in out, "compilation error 2")
>
> --
> 2.7.4
prev parent reply other threads:[~2020-07-20 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 3:19 Jiang, YuX
2020-07-14 3:23 ` Xiao, QimaiX
2020-07-20 7:30 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC82361@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=Jiang@dpdk.org \
--cc=dts@dpdk.org \
--cc=yux.jiang@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).