test suite reviews and discussions
 help / color / mirror / Atom feed
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 V1 2/3] test_plans/power_empty_poll: add test plan	index
Date: Wed, 23 Oct 2019 10:03:47 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB45B75@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191021061129.11958-3-yufengx.mo@intel.com>

Code base changed, please rework

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Monday, October 21, 2019 2:11 PM
> To: dts@dpdk.org; Yao, Lei A <lei.a.yao@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V1 2/3] test_plans/power_empty_poll: add test plan
> index
> 
> 
> 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 | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/test_plans/index.rst b/test_plans/index.rst index
> a10d171..a8a9543 100644
> --- a/test_plans/index.rst
> +++ b/test_plans/index.rst
> @@ -154,6 +154,7 @@ 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
>      vmdq_test_plan
>      vf_l3fwd_test_plan
>      softnic_test_plan
> --
> 2.21.0


  parent reply	other threads:[~2019-10-23 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  6:11 [dts] [PATCH V1 0/3] power_empty_poll: upload automation script and test plan yufengmx
2019-10-21  6:11 ` [dts] [PATCH V1 1/3] tests/power_empty_poll: upload automation script yufengmx
2019-10-21  7:44   ` Yao, Lei A
2019-10-21  6:11 ` [dts] [PATCH V1 2/3] test_plans/power_empty_poll: add test plan index yufengmx
2019-10-21  7:45   ` Yao, Lei A
2019-10-23 10:03   ` Tu, Lijuan [this message]
2019-10-21  6:11 ` [dts] [PATCH V1 3/3] test_plans/power_empty_poll: upload test plan yufengmx
2019-10-21  7:45   ` Yao, Lei A
2019-10-23 10:03   ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB45B75@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).