From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Phanendra Vukkisala <pvukkisala@marvell.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: Vijaya Bhaskar Annayyolla <avijay@marvell.com>,
Faisal Masood <fmasood@marvell.com>
Subject: Re: [dts] [PATCH] crypto: Rebuild DPDK at the end of suite
Date: Fri, 11 Jan 2019 02:00:00 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9FFE27@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1547015245-3044-1-git-send-email-pvukkisala@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Phanendra Vukkisala
> Sent: Wednesday, January 9, 2019 2:28 PM
> To: dts@dpdk.org
> Cc: Vijaya Bhaskar Annayyolla <avijay@marvell.com>; Faisal Masood
> <fmasood@marvell.com>; Phanendra Vukkisala <pvukkisala@marvell.com>
> Subject: [dts] [PATCH] crypto: Rebuild DPDK at the end of suite
>
> From: pvukkisala <pvukkisala@marvell.com>
>
> Crypto tests building DPDK with changes before starting tests and undoing
> changes at end, but missed to rebuild. This patch will take care of rebuilding
> DPDK, so that further tests will not effect while running multiple tests at once
>
> Signed-off-by: phanendra,vukkisala <pvukkisala@marvell.com>
> ---
> tests/TestSuite_crypto_perf.py | 1 +
> tests/TestSuite_unit_tests_cryptodev.py | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/tests/TestSuite_crypto_perf.py b/tests/TestSuite_crypto_perf.py
> index 1715e5c..cf5cce4 100755
> --- a/tests/TestSuite_crypto_perf.py
> +++ b/tests/TestSuite_crypto_perf.py
> @@ -331,6 +331,7 @@ class TestCryptoPerf(TestCase):
> self.dut.send_expect("sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_OPENSSL=y$/CONFIG_RTE_LIBRTE_PMD_OPENS
> SL=n/' config/common_base", "# ")
> self.dut.send_expect("sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y$/CONFIG_RTE_LIBRTE_PMD_AESN
> I_MB=n/' config/common_base", "# ")
> self.dut.send_expect("sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_ZUC=y$/CONFIG_RTE_LIBRTE_PMD_ZUC=n/'
> config/common_base", "# ")
> + self.dut.build_install_dpdk(self.dut.target)
> f.close()
>
> def __check_buffer_size_number(self):
> diff --git a/tests/TestSuite_unit_tests_cryptodev.py
> b/tests/TestSuite_unit_tests_cryptodev.py
> index df83fd9..db6552e 100644
> --- a/tests/TestSuite_unit_tests_cryptodev.py
> +++ b/tests/TestSuite_unit_tests_cryptodev.py
> @@ -105,6 +105,7 @@ class UnitTestsCryptodev(TestCase):
> self.dut.send_expect("sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_OPENSSL=y$/CONFIG_RTE_LIBRTE_PMD_OPENS
> SL=n/' config/common_base", "# ")
> self.dut.send_expect("sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y$/CONFIG_RTE_LIBRTE_PMD_AESN
> I_MB=n/' config/common_base", "# ")
> self.dut.send_expect("sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_ZUC=y$/CONFIG_RTE_LIBRTE_PMD_ZUC=n/'
> config/common_base", "# ")
> + self.dut.build_install_dpdk(self.dut.target)
>
> def test_cryptodev_qat_autotest(self):
> self.__run_unit_test("cryptodev_qat_autotest")
> --
> 1.7.9.5
prev parent reply other threads:[~2019-01-11 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 6:27 Phanendra Vukkisala
2019-01-11 2:00 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0B9FFE27@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=pvukkisala@marvell.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).