From: Rik van Riel <riel@redhat.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
"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 09:38:57 -0400 [thread overview]
Message-ID: <1460381937.25336.8.camel@redhat.com> (raw)
In-Reply-To: <CAJZ5v0i8saPhJ_WsyitJWi3BR4m5f94KV-UnHMmvAWUoLDWfPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]
On Mon, 2016-04-11 at 15:21 +0200, Rafael J. Wysocki wrote:
> On Mon, Apr 11, 2016 at 2:38 PM, Rik van Riel <riel@redhat.com>
> wrote:
> >
> > On Mon, 2016-04-11 at 05:04 +0200, Mike Galbraith wrote:
> > >
> > > 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) ;-)
> > I suspect your pipe benchmark could be very relevant to
> > network performance numbers, too.
> >
> > I would like to go into polling a little bit more aggressively
> > in a future kernel,
> Agreed, but ->
>
> >
> > and I think we can get away with it if we
> > teach the polling loop to exit after we have spent enough time
> > there that the menu governor will pick HLT after a few timed
> > out poll loops.
> -> my concern about this approach is that it would add an artificial
> point to the menu governor statistics at whatever the timeout is
> chosen to be.
I would set the threshold to at least the HLT target residency +
exit latency, so 3 poll timeouts in 8 wakeups would cause
us to fall back to HLT.
On the other hand, if the system is legitimately very busy,
and we break out of the HLT loop due to activities happening
before the timeout most of the time, we should automatically
pick polling.
Does that make sense?
Am I overlooking something?
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-04-11 13:38 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
2016-04-11 12:38 ` Rik van Riel
2016-04-11 13:21 ` Rafael J. Wysocki
2016-04-11 13:38 ` Rik van Riel [this message]
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=1460381937.25336.8.camel@redhat.com \
--to=riel@redhat.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=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).