Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-20 Thread Juri Lelli
On 20/04/18 09:31, Quentin Perret wrote: > On Friday 20 Apr 2018 at 01:14:35 (-0700), Joel Fernandes wrote: > > On Fri, Apr 20, 2018 at 1:13 AM, Joel Fernandes wrote: > > > On Wed, Apr 18, 2018 at 4:17 AM, Quentin Perret > > > wrote: > > >> On Friday 13 Apr 2018 at 16:56:39 (-0700), Joel Fernand

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-20 Thread Quentin Perret
On Friday 20 Apr 2018 at 01:14:35 (-0700), Joel Fernandes wrote: > On Fri, Apr 20, 2018 at 1:13 AM, Joel Fernandes wrote: > > On Wed, Apr 18, 2018 at 4:17 AM, Quentin Perret > > wrote: > >> On Friday 13 Apr 2018 at 16:56:39 (-0700), Joel Fernandes wrote: > >>> Hi, > >>> > >>> On Fri, Apr 6, 2018

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-20 Thread Joel Fernandes
On Fri, Apr 20, 2018 at 1:13 AM, Joel Fernandes wrote: > On Wed, Apr 18, 2018 at 4:17 AM, Quentin Perret > wrote: >> On Friday 13 Apr 2018 at 16:56:39 (-0700), Joel Fernandes wrote: >>> Hi, >>> >>> On Fri, Apr 6, 2018 at 8:36 AM, Dietmar Eggemann >>> wrote: >>> > From: Thara Gopinath >>> > >>>

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-20 Thread Joel Fernandes
On Wed, Apr 18, 2018 at 4:17 AM, Quentin Perret wrote: > On Friday 13 Apr 2018 at 16:56:39 (-0700), Joel Fernandes wrote: >> Hi, >> >> On Fri, Apr 6, 2018 at 8:36 AM, Dietmar Eggemann >> wrote: >> > From: Thara Gopinath >> > >> > Energy-aware scheduling should only operate when the system is not

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-18 Thread Quentin Perret
On Friday 13 Apr 2018 at 16:56:39 (-0700), Joel Fernandes wrote: > Hi, > > On Fri, Apr 6, 2018 at 8:36 AM, Dietmar Eggemann > wrote: > > From: Thara Gopinath > > > > Energy-aware scheduling should only operate when the system is not > > overutilized. There must be cpu time available to place tas

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-17 Thread Leo Yan
On Tue, Apr 17, 2018 at 07:39:21PM +0200, Dietmar Eggemann wrote: > On 04/17/2018 04:25 PM, Leo Yan wrote: > > >>@@ -5394,8 +5416,10 @@ enqueue_task_fair(struct rq *rq, struct task_struct > >>*p, int flags) > >>update_cfs_group(se); > >>} > >>- if (!se) > >>+ if (!se) { > >>

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-17 Thread Dietmar Eggemann
On 04/17/2018 04:25 PM, Leo Yan wrote: @@ -5394,8 +5416,10 @@ enqueue_task_fair(struct rq *rq, struct task_struct *p, int flags) update_cfs_group(se); } - if (!se) + if (!se) { add_nr_running(rq, 1); + update_overutilized_status(rq

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-17 Thread Leo Yan
On Fri, Apr 06, 2018 at 04:36:04PM +0100, Dietmar Eggemann wrote: > From: Thara Gopinath > > Energy-aware scheduling should only operate when the system is not > overutilized. There must be cpu time available to place tasks based on > utilization in an energy-aware fashion, i.e. to pack tasks on

Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-13 Thread Joel Fernandes
Hi, On Fri, Apr 6, 2018 at 8:36 AM, Dietmar Eggemann wrote: > From: Thara Gopinath > > Energy-aware scheduling should only operate when the system is not > overutilized. There must be cpu time available to place tasks based on > utilization in an energy-aware fashion, i.e. to pack tasks on > ene

[RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator

2018-04-06 Thread Dietmar Eggemann
From: Thara Gopinath Energy-aware scheduling should only operate when the system is not overutilized. There must be cpu time available to place tasks based on utilization in an energy-aware fashion, i.e. to pack tasks on energy-efficient cpus without harming the overall throughput. In case the s