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

2017-07-06 Thread Rafael J. Wysocki
On Wednesday, July 05, 2017 09:58:57 AM Juri Lelli wrote: > Hi, > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection for > SCHED_DEADLINE [1]. The set is based on tip/sched/core as of today > (72298e5c92c5), which now already includes Luca's "CPU reclaiming for >

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

2017-07-06 Thread Rafael J. Wysocki
On Wednesday, July 05, 2017 09:58:57 AM Juri Lelli wrote: > Hi, > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection for > SCHED_DEADLINE [1]. The set is based on tip/sched/core as of today > (72298e5c92c5), which now already includes Luca's "CPU reclaiming for >

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

2017-07-06 Thread Peter Zijlstra
On Thu, Jul 06, 2017 at 11:57:15AM -0400, Steven Rostedt wrote: > On Wed, 5 Jul 2017 09:58:57 +0100 > Juri Lelli wrote: > > > Hi, > > > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection > > for > > It would be nice if you specify what "OPP"

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

2017-07-06 Thread Peter Zijlstra
On Thu, Jul 06, 2017 at 11:57:15AM -0400, Steven Rostedt wrote: > On Wed, 5 Jul 2017 09:58:57 +0100 > Juri Lelli wrote: > > > Hi, > > > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection > > for > > It would be nice if you specify what "OPP" stands for. A quick

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

2017-07-06 Thread Juri Lelli
On 06/07/17 11:57, Steven Rostedt wrote: > On Wed, 5 Jul 2017 09:58:57 +0100 > Juri Lelli wrote: > > > Hi, > > > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection > > for > > It would be nice if you specify what "OPP" stands for. A quick google >

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

2017-07-06 Thread Juri Lelli
On 06/07/17 11:57, Steven Rostedt wrote: > On Wed, 5 Jul 2017 09:58:57 +0100 > Juri Lelli wrote: > > > Hi, > > > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection > > for > > It would be nice if you specify what "OPP" stands for. A quick google > search shows "Other

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

2017-07-06 Thread Steven Rostedt
On Wed, 5 Jul 2017 09:58:57 +0100 Juri Lelli wrote: > Hi, > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection for It would be nice if you specify what "OPP" stands for. A quick google search shows "Other Peoples Privates", which isn't the type of

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

2017-07-06 Thread Steven Rostedt
On Wed, 5 Jul 2017 09:58:57 +0100 Juri Lelli wrote: > Hi, > > v1 of the RFC set implementing frequency/cpu invariance and OPP selection for It would be nice if you specify what "OPP" stands for. A quick google search shows "Other Peoples Privates", which isn't the type of selection I would be

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

2017-07-05 Thread Juri Lelli
Hi, v1 of the RFC set implementing frequency/cpu invariance and OPP selection for SCHED_DEADLINE [1]. The set is based on tip/sched/core as of today (72298e5c92c5), which now already includes Luca's "CPU reclaiming for SCHED_DEADLINE". Thanks a lot for reviewing RFCv0! Patches high level

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

2017-07-05 Thread Juri Lelli
Hi, v1 of the RFC set implementing frequency/cpu invariance and OPP selection for SCHED_DEADLINE [1]. The set is based on tip/sched/core as of today (72298e5c92c5), which now already includes Luca's "CPU reclaiming for SCHED_DEADLINE". Thanks a lot for reviewing RFCv0! Patches high level