public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Hu" <hu1.chen@intel.com>
To: rjw@rjwysocki.net
Cc: Chen Hu <hu1.chen@intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [RFC/RFT,v7] cpuidle: New timer events oriented governor for tickless systems
Date: Fri,  7 Dec 2018 15:58:35 +0800	[thread overview]
Message-ID: <20181207075840.5881-1-hu1.chen@intel.com> (raw)
In-Reply-To: <2047881.s5VBHReNGT@aspire.rjw.lan>

From: Chen Hu <hu1.chen@intel.com>

Hi Rafael,

I run several popular Android performance benchmarks on teov7, using kernel
4.19.0 as my baseline because I happen to work on it. To backport teov7 to
kernel 4.19.0, I also backport patch 5f26bdc: "cpuidle: menu: Fix wakeup
statistics updates for polling state". The teov7 doesn't show regressions on
such perf KPIs.

Compare "4.19 + 5f26bdc" and "4.19 + 5f26bdc + teov7" on Android with Intel
Apollo Lake SoC:

Test Case                               Diff after appling teov7
Antutu_6                                0.51%
GFX5_openGL_Car_Chase                   0.43%
GFX5_openGL_Car_Chase_offscreen	        0.25%
GFX5_openGL_Manhattan31	                0.75%
GFX5_openGL_Manhattan31_1080_offscreen  -0.10%
Geekbench3.3                            -0.13%
H264_1080P_60FPS                        0.00%
H264_2160P_60FPS                        0.00%
H265_2K_10bit                           0.00%
H265_2K_8bit                            0.00%
Resume_time                             1.31%
full_boot                               -0.39%

Thanks
Chen Hu

  reply	other threads:[~2018-12-07  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 18:35 [RFC/RFT][PATCH v7] cpuidle: New timer events oriented governor for tickless systems Rafael J. Wysocki
2018-12-07  7:58 ` Chen, Hu [this message]
2018-12-07  8:27   ` [RFC/RFT,v7] " Rafael J. Wysocki
2018-12-07  9:37   ` Quentin Perret

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=20181207075840.5881-1-hu1.chen@intel.com \
    --to=hu1.chen@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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