From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Rik van Riel <riel@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Doug Smythies <dsmythies@telus.net>
Subject: Re: [regression] cross core scheduling frequency drop bisected to 0c313cb20732
Date: Mon, 11 Apr 2016 05:04:54 +0200 [thread overview]
Message-ID: <1460343894.3682.11.camel@gmail.com> (raw)
In-Reply-To: <1460319890.25336.2.camel@redhat.com>
On Sun, 2016-04-10 at 16:24 -0400, Rik van Riel wrote:
> On Sun, 2016-04-10 at 17:39 +0200, Mike Galbraith wrote:
> > Should the default idle state not then be governor dependent? When I
> > set gov=performance, I'm expecting box to go just as fast as it can
> > go
> > without melting. Does polling risk CPU -> lava conversion?
>
> Current CPUs can only have some cores run at full speed
> (turbo mode) if other cores are idling and/or running at
> lower speeds.
The real world is very unlikely to miss the prettier numbers I'm
grieving over one tiny bit. Knowing that doesn't make giving them up
any easier though.. byebye cycles (sniff) ;-)
-Mike
next prev parent reply other threads:[~2016-04-11 3:04 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
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 [this message]
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=1460343894.3682.11.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=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=rafael@kernel.org \
--cc=riel@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).