All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Paul Turner <pjt@google.com>, Len Brown <len.brown@intel.com>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	Andi Kleen <andi.kleen@intel.com>,
	Rafael Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [RFC PATCH 0/3] CFS idle injection
Date: Wed, 4 Nov 2015 10:43:50 -0800	[thread overview]
Message-ID: <20151104184348.GA12825@localhost.localdomain> (raw)
In-Reply-To: <1446656752.7814.119.camel@spandruv-desk3.jf.intel.com>

Hello Jacob, Srinivas,

On Wed, Nov 04, 2015 at 09:05:52AM -0800, Srinivas Pandruvada wrote:
> On Wed, 2015-11-04 at 08:58 -0800, Jacob Pan wrote:

<cut>
> > > > I have two choices for this code:
> > > > 1) be part of existing powerclamp driver but require exporting some
> > > >    sched APIs.
> > > > 2) be part of sched since the genernal rule applies when it comes
> > > > down to sycnhronized idle time for best power savings.
> > > > 
> > > > The patches below are for #2. There is a known problem with LOW RES
> > > > timer mode that I am working on. But I am hoping to get review
> > > > earlier.
> > > > 
> > > 
> > > I also like #2 too. Specially now that it is not limited to a specific
> > > platform. One question though, could you still keep the cooling device
> > > support of it? In some systems, it might make sense to enable /
> > > disable idle injections based on temperature.
> > > 
> > One of the key difference between 1 and 2 is that #2 is open loop
> > control, since we don't have CPU c-states info baked into scheduler. To
> > close the loop, perhaps we can export some internal APIs to the thermal
> > subsystem then the thermal governors can pick the condition to inject
> > idle.


Jacob,

I also like this direction. Having the proper APIs exported, creating a
cooling device that use them would be  natural path. Then, one could
create a thermal zone plugging a governor and the idle injection cooling
device that uses the exported APIs.

> > > Was there any particular reason you dropped the cooling device
> > > support?
> > > 
> > I did sysctl instead of thermal sysfs to conform the rest of the sched
> > tuning knobs. We could also have a proxy cooling device to call
> > internal APIs mentioned above.

Agreed here then.


> I think we should have cooling device as we are already using this
> cooling device. Once it pass RFC stage,I think we should consider add
> this.

Srinivas, 
Yes, that seens to be a good path to follow. Thanks.


> Thanks,
> Srinivas
> > 
> > Another reason is that, I intend to extend beyond thermal. Where we can
> > consolidate/sync idle work in semi-active and balanced workload.

I see. 

BR,

Eduardo Valentin

  reply	other threads:[~2015-11-04 18:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  0:10 [RFC PATCH 0/3] CFS idle injection Jacob Pan
2015-11-03  0:10 ` [RFC PATCH 1/3] ktime: add a roundup function Jacob Pan
2015-11-03  0:10 ` [RFC PATCH 2/3] timer: relax tick stop in idle entry Jacob Pan
2015-11-03  0:10 ` [RFC PATCH 3/3] sched: introduce synchronized idle injection Jacob Pan
2015-11-03 13:31   ` Peter Zijlstra
2015-11-03 14:16     ` Jacob Pan
2015-11-03 16:45     ` Jacob Pan
2015-11-05 10:09       ` Peter Zijlstra
2015-11-05 14:22         ` Arjan van de Ven
2015-11-05 14:33           ` Peter Zijlstra
2015-11-05 14:48             ` Peter Zijlstra
2015-11-05 15:28             ` Arjan van de Ven
2015-11-05 16:52               ` Peter Zijlstra
2015-11-05 18:55                 ` Thomas Gleixner
2015-11-05 18:47               ` Thomas Gleixner
2015-11-05 15:32             ` Jacob Pan
2015-11-05 16:06               ` Arjan van de Ven
2015-11-05 19:27         ` Jacob Pan
2015-11-05 19:32           ` Jacob Pan
2015-11-05 13:59     ` Peter Zijlstra
2015-11-05 23:36       ` Jacob Pan
2015-11-06  7:45         ` Peter Zijlstra
2015-11-06 23:49           ` Jacob Pan
2015-11-10  0:19             ` Jacob Pan
2015-11-04  6:06 ` [RFC PATCH 0/3] CFS " Eduardo Valentin
2015-11-04 16:58   ` Jacob Pan
2015-11-04 17:05     ` Srinivas Pandruvada
2015-11-04 18:43       ` Eduardo Valentin [this message]
2015-11-05 10:12     ` Peter Zijlstra
2015-11-06 16:50       ` Punit Agrawal
2015-11-06 19:18         ` Jacob Pan
2015-11-09 11:56           ` Punit Agrawal
2015-11-09 14:15             ` Peter Zijlstra
2015-11-09 14:43               ` Jacob Pan
2015-11-10 10:07               ` Juri Lelli
2015-11-10 10:34                 ` Peter Zijlstra
2015-11-10 10:56                   ` Juri Lelli
2015-11-09 14:36             ` Jacob Pan
2015-11-06 18:30       ` Dietmar Eggemann
2015-11-06 19:10         ` Jacob Pan
2015-11-06 21:55           ` Dietmar Eggemann
2015-11-09 21:23             ` Jacob Pan
2015-11-09 21:45               ` Peter Zijlstra

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=20151104184348.GA12825@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=andi.kleen@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.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 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.