All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: 'Kristen Carlson Accardi' <kristen@linux.intel.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org
Subject: RE: [PATCH 0/5] intel_pstate: Use C0 time, calculate target pstate directly
Date: Mon, 13 Apr 2015 14:16:10 -0700	[thread overview]
Message-ID: <001a01d0762f$117316c0$34594440$@net> (raw)
In-Reply-To: <20150413093214.63dc6184@kcaccard-desk.amr.corp.intel.com>

Hi Kristen,

Thanks for your quick and positive reply.

On 2015.04.13 09:32 Kristen wrote:
> On Sat, 11 Apr 2015 21:10:25 -0700 Doug Smythies wrote:

> Thanks for your patches, I'll be doing some testing and review and let
> you know how things go.

And from the other thread:

> I'm going to need to do a lot of
> benchmarking on a variety of platforms to make sure we haven't regressed
> anything.

Yes, of course.

I make no claim to have found the best default operating parameters,
IIR gain, c0_floor, c0_ceiling, sample_rate_ms.

I only have a i7-2600K to test with.

Other results:

Phoronix: Kernel compile:
acpi-cpufreq: 122.4 seconds
4.0RC7, unpatched: 121.8 seconds
Patched: 122.4 seconds

Phoronix: Apache:
acpi-cpufreq: 19429
4.0RC7, unpatched: 20089
Patched: 20410

Phoronix: ffmpeg:
acpi-cpufreq: 17.06 seconds and 1444.36 Joules Package Energy.
4.0RC7, unpatched: 17.65 seconds and 1444.36 Joules
Patched: 23.1 seconds and 1302 Joules

Note: Dirk proved that the ffmpeg test does odd switching of CPUs
when they become 50% loaded. With the settings I have used for c0_floor
and c0_ceiling, these results are not a surprise. 
 
2000 Seconds idle (server): 
Unpatched: 7704 Joules
Patched: 7625 Joules.

An i5-4690K running some Ubuntu desktop, but otherwise idle:
Average CPU frequency goes way down and power consumption drops by just over half a watt.

An i7-4790K running xorg and Arch distro, but otherwise idle:
Average CPU frequency drops considerably, and power consumption is about the same.
Note: unpatched CPU frequencies were not as high as previously reported on that bugzilla report.
I do not know why.
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=93521

Still waiting to hear from the other i7-4790K user that had high CPU frequency when idle issues.

There is a bit of evidence that the unpatched reference kernel might do a little
better at holding CPU frequencies lower in the low load 20 Hz work / sleep frequency range.
I'm still looking at that scenario.

There are many graphs at:
Double u double u double u dot smythies dot com /~doug/linux/intel_pstate/build220/index.html

... Doug



  reply	other threads:[~2015-04-13 21:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12  4:10 [PATCH 0/5] intel_pstate: Use C0 time, calculate target pstate directly Doug Smythies
2015-04-12  4:10 ` [PATCH 1/5] intel_pstate: Add tsc collection and keep previous target pstate. Add both to trace Doug Smythies
2015-04-29 16:57   ` Kristen Carlson Accardi
2015-05-04 23:34     ` Rafael J. Wysocki
2015-04-12  4:10 ` [PATCH 2/5] intel_pstate: Use C0 time for busy calculations (again) Doug Smythies
2015-05-06 19:20   ` Kristen Carlson Accardi
2015-05-07  6:17     ` Doug Smythies
2015-04-12  4:10 ` [PATCH 3/5] intel_pstate: Calculate target pstate directly Doug Smythies
2015-04-12  4:10 ` [PATCH 4/5] intel_pstate: Compensate for intermediate durations (v2) Doug Smythies
2015-04-12  4:10 ` [PATCH 5/5] intel_pstate: Adjust default IIR filter gain Doug Smythies
2015-04-13 16:32 ` [PATCH 0/5] intel_pstate: Use C0 time, calculate target pstate directly Kristen Carlson Accardi
2015-04-13 21:16   ` Doug Smythies [this message]
2015-04-16 16:35 ` Doug Smythies
2015-04-17  0:46   ` Rafael J. Wysocki

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='001a01d0762f$117316c0$34594440$@net' \
    --to=dsmythies@telus.net \
    --cc=kristen@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.