test suite reviews and discussions
 help / color / mirror / Atom feed
From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lei.a.yao@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V2 0/3] power_empty_poll: upload automation script and test plan
Date: Thu, 24 Oct 2019 09:39:31 +0800	[thread overview]
Message-ID: <20191024013934.67412-1-yufengx.mo@intel.com> (raw)

 For packet processing workloads such as DPDK polling is continuous. 
 This means CPU cores always show 100% busy independent of how much work 
 those cores are doing. It is critical to accurately determine how busy 
 a core is hugely important for the following reasons. 

v2: 
 - fix trailing whitespace warning 
 - rebase code to resolve merge conflict issue. 

yufengmx (3):
  tests/power_empty_poll: upload automation script
  test_plans/power_empty_poll: add test plan index
  test_plans/power_empty_poll: upload test plan

 test_plans/index.rst                      |   2 +
 test_plans/power_empty_poll_test_plan.rst | 138 +++++++++
 tests/TestSuite_power_empty_poll.py       | 359 ++++++++++++++++++++++
 3 files changed, 499 insertions(+)
 create mode 100644 test_plans/power_empty_poll_test_plan.rst
 create mode 100644 tests/TestSuite_power_empty_poll.py

-- 
2.21.0


             reply	other threads:[~2019-10-24  1:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  1:39 yufengmx [this message]
2019-10-24  1:39 ` [dts] [PATCH V2 1/3] tests/power_empty_poll: upload automation script yufengmx
2019-10-24  1:39 ` [dts] [PATCH V2 2/3] test_plans/power_empty_poll: add test plan index yufengmx
2019-10-24  1:39 ` [dts] [PATCH V2 3/3] test_plans/power_empty_poll: upload test plan yufengmx
2019-11-04  2:37 ` [dts] [PATCH V2 0/3] power_empty_poll: upload automation script and " 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=20191024013934.67412-1-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    --cc=lei.a.yao@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).