linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: 'Mike Galbraith' <umgwanakikbuti@gmail.com>
Cc: 'Peter Zijlstra' <peterz@infradead.org>,
	"'Rafael J. Wysocki'" <rafael.j.wysocki@intel.com>,
	'LKML' <linux-kernel@vger.kernel.org>,
	'Linux PM list' <linux-pm@vger.kernel.org>,
	'Rik van Riel' <riel@redhat.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Subject: RE: [regression] cross core scheduling frequency drop bisected to 0c313cb20732
Date: Sat, 9 Apr 2016 00:17:52 -0700	[thread overview]
Message-ID: <001e01d1922f$ef219a10$cd64ce30$@net> (raw)
In-Reply-To: <001101d191e4$b00602d0$10120870$@net>

On 2016.04.08 15:19 Doug Smythies wrote:
> On 2016.04.08 14:00 Rafael J. Wysocki wrote:
>> On Friday, April 08, 2016 08:50:54 AM Mike Galbraith wrote:
>>> On Fri, 2016-04-08 at 08:45 +0200, Peter Zijlstra wrote:
>>> 
>>>> Cute, I thought you used governor=performance for your runs?
>>> 
>>> I do, and those numbers are with it thus set.

>> Well, this is a trade-off.
>>
>> 4.5 introduced a power regression here so this one goes back to the previous
>> state of things.

> Mike:
>
> Could you send me, or point me to, the program "pipe-test"?
> So far, I have only found one, but it is both old and not
> the same program you are running (based on print statements).
>
> I realize I might not be to recreate your problem scenario anyhow,
> I just want to try.

I still didn't find the exact same program, but I think I found some
earlier version of the correct test.

I get (long term average):
Kernel 4.4.0-17: Powersave 3.93 usecs/loop ; Performance 3.93 usecs/loop 0.89
Kernel 4.5-rc7: Powersave 3.47 usecs/loop ; Performance 3.51 usecs/loop  1.00
Kernel 4.6-rc1: Powersave 3.84 usecs/loop ; Performance 3.88 usecs/loop  0.90

So, similar results (so far, I didn't try reverted yet).

... Doug

  parent reply	other threads:[~2016-04-09  7:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1460092854.4051.1.camel@gmail.com>
     [not found] ` <20160408064510.GK3448@twins.programming.kicks-ass.net>
     [not found]   ` <1460098254.5582.17.camel@gmail.com>
2016-04-08 20:59     ` [regression] cross core scheduling frequency drop bisected to 0c313cb20732 Rafael J. Wysocki
2016-04-08 22:19       ` Doug Smythies
2016-04-09  6:44         ` Mike Galbraith
2016-04-09  7:17         ` Doug Smythies [this message]
2016-04-09  7:27           ` Mike Galbraith
2016-04-09 11:08         ` Peter Zijlstra
2016-04-09  6:40       ` Mike Galbraith
2016-04-09 12:33         ` Rafael J. Wysocki
2016-04-09 15:10           ` Mike Galbraith
2016-04-09 16:39             ` Mike Galbraith
2016-04-10  3:44               ` Rafael J. Wysocki
2016-04-10  7:16                 ` Doug Smythies
2016-04-10  9:35                 ` Mike Galbraith
2016-04-10 14:54                   ` Mike Galbraith
2016-04-09 11:07       ` Peter Zijlstra
2016-04-09 12:31         ` Rafael J. Wysocki
2016-04-10 15:39           ` Mike Galbraith
2016-04-10 20:24             ` Rik van Riel
2016-04-11  3:04               ` Mike Galbraith
2016-04-11 12:38                 ` Rik van Riel
2016-04-11 13:21                   ` Rafael J. Wysocki
2016-04-11 13:38                     ` Rik van Riel

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='001e01d1922f$ef219a10$cd64ce30$@net' \
    --to=dsmythies@telus.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=riel@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=umgwanakikbuti@gmail.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).