From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>, "Yao, Lei A" <lei.a.yao@intel.com>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V3 0/4] power_branch_ratio: upload suite test plan and script
Date: Mon, 1 Jun 2020 03:12:47 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC565DE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200525022258.3171-1-yufengx.mo@intel.com>
Applied the series, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Monday, May 25, 2020 10:23 AM
> To: dts@dpdk.org; Yao, Lei A <lei.a.yao@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V3 0/4] power_branch_ratio: upload suite test plan and
> script
>
> Based on the branch ratio info offered by CPU, the DPDK user can know if
> the CPU's real workload is high or Low. Then the host server can adjust the
> related CPU frequency base this indicator.
>
> v3:
> - update test plan and script.
> - add compile switch description
> - change power driver intel_pstate from disable to enable.
> - add more branch ratio information output description.
>
> v2:
> - python3 support.
> - use pktgen new callback function to take the place of shell script query.
> - display dpdk version.
> - remove un-used parameters.
> - update comment.
>
> yufengmx (4):
> conf/power_branch_ratio: virtual machine configuration
> test_plans/power_branch_ratio: add test plan index
> test_plans/power_branch_ratio: upload test plan
> tests/power_branch_ratio: upload automation script
>
> conf/power_branch_ratio.cfg | 30 +
> test_plans/index.rst | 1 +
> test_plans/power_branch_ratio_test_plan.rst | 178 +++++
> tests/TestSuite_power_branch_ratio.py | 679 ++++++++++++++++++++
> 4 files changed, 888 insertions(+)
> create mode 100644 conf/power_branch_ratio.cfg create mode 100644
> test_plans/power_branch_ratio_test_plan.rst
> create mode 100644 tests/TestSuite_power_branch_ratio.py
>
> --
> 2.21.0
prev parent reply other threads:[~2020-06-01 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 2:22 yufengmx
2020-05-25 2:22 ` [dts] [PATCH V3 1/4] conf/power_branch_ratio: virtual machine configuration yufengmx
2020-05-26 2:15 ` Yao, Lei A
2020-05-25 2:22 ` [dts] [PATCH V3 2/4] test_plans/power_branch_ratio: add test plan index yufengmx
2020-05-25 2:22 ` [dts] [PATCH V3 3/4] test_plans/power_branch_ratio: upload test plan yufengmx
2020-05-25 2:22 ` [dts] [PATCH V3 4/4] tests/power_branch_ratio: upload automation script yufengmx
2020-06-01 3:12 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC565DE@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=yufengx.mo@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).