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
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
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
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
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
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
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
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
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
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
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(),
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(),
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
>
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
>
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
> >
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
> >
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
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
18 matches
Mail list logo