From: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] tests: clean and reset the hugepages to fix cryptodev perf drop
Date: Tue, 19 May 2020 02:20:19 +0000 [thread overview]
Message-ID: <f8a3e1474d3640a1bcc142f1cc729504@intel.com> (raw)
In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BC3ED4D@SHSMSX101.ccr.corp.intel.com>
There is enough hugepage left, but the perf of scheduler+qat dropped.
and add this action, the issue disappeared.
-----Original Message-----
From: Tu, Lijuan
Sent: Tuesday, May 19, 2020 9:53 AM
To: Zhao, XinfengX <xinfengx.zhao@intel.com>; dts@dpdk.org
Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
Subject: RE: [dts] [PATCH] tests: clean and reset the hugepages to fix cryptodev perf drop
Why do you add this? Is there anyone occupied many hugepages and don't release them?
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xinfengx
> Sent: Friday, May 15, 2020 2:38 AM
> To: dts@dpdk.org
> Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
> Subject: [dts] [PATCH] tests: clean and reset the hugepages to fix
> cryptodev perf drop
>
> Signed-off-by: xinfengx <xinfengx.zhao@intel.com>
> ---
> tests/TestSuite_crypto_perf_cryptodev_perf.py | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tests/TestSuite_crypto_perf_cryptodev_perf.py
> b/tests/TestSuite_crypto_perf_cryptodev_perf.py
> index defb7c2..910c81a 100644
> --- a/tests/TestSuite_crypto_perf_cryptodev_perf.py
> +++ b/tests/TestSuite_crypto_perf_cryptodev_perf.py
> @@ -71,6 +71,11 @@ class PerfTestsCryptodev(TestCase):
> }
> self._app_path =
> "./x86_64-native-linuxapp-gcc/build/app/test-crypto-
> perf/dpdk-test-crypto-perf"
>
> + page_size = self.dut.send_expect("awk '/Hugepagesize/ {print $2}'
> /proc/meminfo", "# ")
> + if int(page_size) == 1024 * 1024:
> + self.dut.send_expect('echo 0 >
> /sys/kernel/mm/hugepages/hugepages-%skB/nr_hugepages' % (page_size),
> '# ', 5)
> + self.dut.send_expect('echo 16 >
> /sys/kernel/mm/hugepages/hugepages-%skB/nr_hugepages' % (page_size),
> '# ', 5)
> +
> if not cc.is_build_skip(self):
> cc.build_dpdk_with_cryptodev(self)
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-05-19 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 18:37 xinfengx
2020-05-15 2:11 ` Zhao, XinfengX
2020-05-19 1:53 ` Tu, Lijuan
2020-05-19 2:20 ` Zhao, XinfengX [this message]
2020-05-19 2: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=f8a3e1474d3640a1bcc142f1cc729504@intel.com \
--to=xinfengx.zhao@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@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).