test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yinan <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Wang Yinan <yinan.wang@intel.com>
Subject: [dts] [PATCH v1] test_plans: add test plan for power managerment throughput test
Date: Thu, 27 Jun 2019 20:04:45 +0000	[thread overview]
Message-ID: <20190627200445.100198-1-yinan.wang@intel.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=Y, Size: 3625 bytes --]

From: Wang Yinan <yinan.wang@intel.com>

Signed-off-by: Wang Yinan <yinan.wang@intel.com>
---
 ...power_managerment_throughput_test_plan.rst | 74 +++++++++++++++++++
 1 file changed, 74 insertions(+)
 create mode 100644 test_plans/power_managerment_throughput_test_plan.rst

diff --git a/test_plans/power_managerment_throughput_test_plan.rst b/test_plans/power_managerment_throughput_test_plan.rst
new file mode 100644
index 0000000..a9234be
--- /dev/null
+++ b/test_plans/power_managerment_throughput_test_plan.rst
@@ -0,0 +1,74 @@
+.. Copyright (c) <2019>, Intel Corporation
+   All rights reserved.
+
+   Redistribution and use in source and binary forms, with or without
+   modification, are permitted provided that the following conditions
+   are met:
+
+   - Redistributions of source code must retain the above copyright
+     notice, this list of conditions and the following disclaimer.
+
+   - Redistributions in binary form must reproduce the above copyright
+     notice, this list of conditions and the following disclaimer in
+     the documentation and/or other materials provided with the
+     distribution.
+
+   - Neither the name of Intel Corporation nor the names of its
+     contributors may be used to endorse or promote products derived
+     from this software without specific prior written permission.
+
+   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+   FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+   COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+   INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+   (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+   SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+   OF THE POSSIBILITY OF SUCH DAMAGE.
+
+======================================
+Power managerment throughput test plan
+======================================
+
+This test plan test cpu frequence changed according io workloads with l3fwd-power sample.
+The cpu frequency status depends on NIC and CPU type.
+
+Prerequisites
+=============
+
+1. Update Grub::
+
+    Add "intel_pstate=disable" in kernel options.
+
+2. BIOS configuration as below::
+
+    CPU mode : "Power"
+    Workload configuratuion:"IO sensitive"
+    Hardware Power : "Disabled"
+    Speedstep : "Enabled"
+    Turbo : "Enabled"
+    C-stats:C0/C1
+    C6 : "Enabled"
+
+Test Case1: Check the CPU frequency can change according differernt packet speed
+================================================================================
+
+1. Check that you are using the "acpi-cpufreq" driver by command "cpufreq-info".
+
+2. CPU frequency controlled by userspace by command "cpupower frequency-set -g userspace".
+
+3. Bind one nic port to igb_uio, launch l3fwd-power sample, one core used for one port::
+
+    ./l3fwd-power -c 0xc000000 -n 4 -- -P -p 0x01  --config '(0,0,27)'
+
+4. Send packets by packet generator with high speed, check the used cpu frequency is almost 100%::
+
+    cat /sys/devices/system/cpu/cpu27/cpufreq/cpuinfo_cur_freq
+
+5. Send packets by packet generator with low speed, the CPU frequency will reduce about 50%::
+
+    cat /sys/devices/system/cpu/cpu27/cpufreq/cpuinfo_cur_freq
\ No newline at end of file
-- 
2.17.1


             reply	other threads:[~2019-06-28  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 20:04 Yinan [this message]
2019-07-10  6:16 ` 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=20190627200445.100198-1-yinan.wang@intel.com \
    --to=yinan.wang@intel.com \
    --cc=dts@dpdk.org \
    /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).