Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Peter Zijlstra
On Wed, May 24, 2017 at 10:50:53AM +0100, Juri Lelli wrote: > Agreed. However, problem seems to be that > > - in my opinion (current implementation) this translated into scaling >runtime considering current freq and cpu-max-capacity; and this is >required when frequency scaling is

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Peter Zijlstra
On Wed, May 24, 2017 at 10:50:53AM +0100, Juri Lelli wrote: > Agreed. However, problem seems to be that > > - in my opinion (current implementation) this translated into scaling >runtime considering current freq and cpu-max-capacity; and this is >required when frequency scaling is

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Peter Zijlstra
On Wed, May 24, 2017 at 12:01:51PM +0200, Luca Abeni wrote: > > > So I'm terribly confused... > > > > > > By using the active bandwidth to select frequency we effectively > > > reduce idle time (to 0 if we had infinite granular frequency steps > > > and no margins). > > > > > > So !RECLAIM works

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Peter Zijlstra
On Wed, May 24, 2017 at 12:01:51PM +0200, Luca Abeni wrote: > > > So I'm terribly confused... > > > > > > By using the active bandwidth to select frequency we effectively > > > reduce idle time (to 0 if we had infinite granular frequency steps > > > and no margins). > > > > > > So !RECLAIM works

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Luca Abeni
On Wed, 24 May 2017 10:25:05 +0100 Juri Lelli wrote: > Hi, > > On 23/05/17 22:23, Peter Zijlstra wrote: > > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > > > A point that is still very much up for discussion (more that the > > > others :) is how we

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Luca Abeni
On Wed, 24 May 2017 10:25:05 +0100 Juri Lelli wrote: > Hi, > > On 23/05/17 22:23, Peter Zijlstra wrote: > > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > > > A point that is still very much up for discussion (more that the > > > others :) is how we implement frequency/cpu

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Juri Lelli
On 24/05/17 11:41, Peter Zijlstra wrote: > On Wed, May 24, 2017 at 10:25:05AM +0100, Juri Lelli wrote: > > Hi, > > > > On 23/05/17 22:23, Peter Zijlstra wrote: > > > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > > > > > A point that is still very much up for discussion (more

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Juri Lelli
On 24/05/17 11:41, Peter Zijlstra wrote: > On Wed, May 24, 2017 at 10:25:05AM +0100, Juri Lelli wrote: > > Hi, > > > > On 23/05/17 22:23, Peter Zijlstra wrote: > > > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > > > > > A point that is still very much up for discussion (more

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Peter Zijlstra
On Wed, May 24, 2017 at 10:25:05AM +0100, Juri Lelli wrote: > Hi, > > On 23/05/17 22:23, Peter Zijlstra wrote: > > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > > > A point that is still very much up for discussion (more that the others > > > :) is > > > how we implement

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Peter Zijlstra
On Wed, May 24, 2017 at 10:25:05AM +0100, Juri Lelli wrote: > Hi, > > On 23/05/17 22:23, Peter Zijlstra wrote: > > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > > > A point that is still very much up for discussion (more that the others > > > :) is > > > how we implement

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Juri Lelli
Hi, On 23/05/17 22:23, Peter Zijlstra wrote: > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > A point that is still very much up for discussion (more that the others :) > > is > > how we implement frequency/cpu scaling. SCHED_FLAG_RECLAIM tasks only need > > grub_reclaim(),

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-24 Thread Juri Lelli
Hi, On 23/05/17 22:23, Peter Zijlstra wrote: > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > A point that is still very much up for discussion (more that the others :) > > is > > how we implement frequency/cpu scaling. SCHED_FLAG_RECLAIM tasks only need > > grub_reclaim(),

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-23 Thread Peter Zijlstra
On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > A point that is still very much up for discussion (more that the others :) is > how we implement frequency/cpu scaling. SCHED_FLAG_RECLAIM tasks only need > grub_reclaim(), as the function already scales their reservation runtime >

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-23 Thread Peter Zijlstra
On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > A point that is still very much up for discussion (more that the others :) is > how we implement frequency/cpu scaling. SCHED_FLAG_RECLAIM tasks only need > grub_reclaim(), as the function already scales their reservation runtime >

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-23 Thread Peter Zijlstra
On Tue, May 23, 2017 at 10:23:21PM +0200, Peter Zijlstra wrote: > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > A point that is still very much up for discussion (more that the others :) > > is > > how we implement frequency/cpu scaling. SCHED_FLAG_RECLAIM tasks only need > >

Re: [PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-23 Thread Peter Zijlstra
On Tue, May 23, 2017 at 10:23:21PM +0200, Peter Zijlstra wrote: > On Tue, May 23, 2017 at 09:53:43AM +0100, Juri Lelli wrote: > > > A point that is still very much up for discussion (more that the others :) > > is > > how we implement frequency/cpu scaling. SCHED_FLAG_RECLAIM tasks only need > >

[PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-23 Thread Juri Lelli
Hi, this RFC set implements frequency/cpu invariance and OPP selection for SCHED_DEADLINE. The set has been slightly tested on a Juno platform. The current incarnation of the patches stems both from previous RFD[1] review comments and discussion at OSPM-summit[2], during which we seemed to agree

[PATCH RFC 0/8] SCHED_DEADLINE freq/cpu invariance and OPP selection

2017-05-23 Thread Juri Lelli
Hi, this RFC set implements frequency/cpu invariance and OPP selection for SCHED_DEADLINE. The set has been slightly tested on a Juno platform. The current incarnation of the patches stems both from previous RFD[1] review comments and discussion at OSPM-summit[2], during which we seemed to agree