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 2/3] test_plans/power_empty_poll: add test plan index
Date: Thu, 24 Oct 2019 09:39:33 +0800 [thread overview]
Message-ID: <20191024013934.67412-3-yufengx.mo@intel.com> (raw)
In-Reply-To: <20191024013934.67412-1-yufengx.mo@intel.com>
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.
Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
test_plans/index.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/test_plans/index.rst b/test_plans/index.rst
index 4dde8e6..9c305e4 100644
--- a/test_plans/index.rst
+++ b/test_plans/index.rst
@@ -154,7 +154,9 @@ The following are the test plans for the DPDK DTS automated test system.
vhost_qemu_mtu_test_plan
vhost_user_live_migration_test_plan
vm_power_manager_test_plan
+ power_empty_poll_test_plan
power_pbf_test_plan
+ power_pstate_test_plan
vmdq_test_plan
vf_l3fwd_test_plan
softnic_test_plan
--
2.21.0
next prev parent reply other threads:[~2019-10-24 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 1:39 [dts] [PATCH V2 0/3] power_empty_poll: upload automation script and test plan yufengmx
2019-10-24 1:39 ` [dts] [PATCH V2 1/3] tests/power_empty_poll: upload automation script yufengmx
2019-10-24 1:39 ` yufengmx [this message]
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-3-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).