Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-10-08 Thread Juri Lelli
On 08/10/15 01:14, Steve Muckle wrote: > On 08/25/2015 03:45 AM, Juri Lelli wrote: >> But, it is true that if the above events happened the other way around >> (we trigger an update after load balancing and a new task arrives), we >> may miss the opportunity to jump to max with the new task. In my

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-10-07 Thread Steve Muckle
On 08/25/2015 03:45 AM, Juri Lelli wrote: > But, it is true that if the above events happened the other way around > (we trigger an update after load balancing and a new task arrives), we > may miss the opportunity to jump to max with the new task. In my mind > this is probably not a big deal, as w

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-09-28 Thread Steve Muckle
Hi Punit, On 09/28/2015 09:48 AM, Punit Agrawal wrote: > Hi Mike, > > I ran into an issue when using this patch. Posting it here as this is > the latest posting I can find. > > Morten Rasmussen writes: > >> From: Michael Turquette >> ... >> diff --git a/include/linux/cpufreq.h b/include/linux

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-09-28 Thread Punit Agrawal
Hi Mike, I ran into an issue when using this patch. Posting it here as this is the latest posting I can find. Morten Rasmussen writes: > From: Michael Turquette > > Scheduler-driven cpu frequency selection is desirable as part of the > on-going effort to make the scheduler better aware of ener

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-09-15 Thread Juri Lelli
On 15/09/15 14:45, Peter Zijlstra wrote: > On Mon, Sep 14, 2015 at 04:57:35PM +0100, Juri Lelli wrote: >> On 04/09/15 14:27, Juri Lelli wrote: >>> So, just to recall what we discussed at LPC (I have Mike's slides >>> at hand :-)). It seems that key points are: >>> >>> 1- we agreed that locking in c

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-09-15 Thread Peter Zijlstra
On Mon, Sep 14, 2015 at 04:57:35PM +0100, Juri Lelli wrote: > On 04/09/15 14:27, Juri Lelli wrote: > > So, just to recall what we discussed at LPC (I have Mike's slides > > at hand :-)). It seems that key points are: > > > > 1- we agreed that locking in cpufreq core has to change as we > >have

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-09-14 Thread Juri Lelli
On 04/09/15 14:27, Juri Lelli wrote: > On 15/08/15 13:35, Peter Zijlstra wrote: >> On Tue, Jul 07, 2015 at 07:24:21PM +0100, Morten Rasmussen wrote: >>> diff --git a/kernel/sched/cpufreq_sched.c b/kernel/sched/cpufreq_sched.c >>> new file mode 100644 >>> index 000..5020f24 >>> --- /dev/null >>>

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-09-04 Thread Juri Lelli
On 15/08/15 13:35, Peter Zijlstra wrote: > On Tue, Jul 07, 2015 at 07:24:21PM +0100, Morten Rasmussen wrote: >> diff --git a/kernel/sched/cpufreq_sched.c b/kernel/sched/cpufreq_sched.c >> new file mode 100644 >> index 000..5020f24 >> --- /dev/null >> +++ b/kernel/sched/cpufreq_sched.c >> @@ -0,

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-08-25 Thread Juri Lelli
Hi Peter, On 15/08/15 14:05, Peter Zijlstra wrote: > On Tue, Jul 07, 2015 at 07:24:21PM +0100, Morten Rasmussen wrote: >> +void cpufreq_sched_set_cap(int cpu, unsigned long capacity) >> +{ >> +unsigned int freq_new, cpu_tmp; >> +struct cpufreq_policy *policy; >> +struct gov_data *gd; >

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-08-15 Thread Peter Zijlstra
On Tue, Jul 07, 2015 at 07:24:21PM +0100, Morten Rasmussen wrote: > diff --git a/kernel/sched/cpufreq_sched.c b/kernel/sched/cpufreq_sched.c > new file mode 100644 > index 000..5020f24 > --- /dev/null > +++ b/kernel/sched/cpufreq_sched.c > @@ -0,0 +1,308 @@ > +/* > + * Copyright (C) 2015 Mich

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-08-15 Thread Peter Zijlstra
On Tue, Jul 07, 2015 at 07:24:21PM +0100, Morten Rasmussen wrote: > +void cpufreq_sched_set_cap(int cpu, unsigned long capacity) > +{ > + unsigned int freq_new, cpu_tmp; > + struct cpufreq_policy *policy; > + struct gov_data *gd; > + unsigned long capacity_max = 0; > + > + /* up

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-08-11 Thread Juri Lelli
Hi, On 11/08/15 03:14, Leo Yan wrote: > On Tue, Jul 07, 2015 at 07:24:21PM +0100, Morten Rasmussen wrote: >> From: Michael Turquette >> >> Scheduler-driven cpu frequency selection is desirable as part of the >> on-going effort to make the scheduler better aware of energy >> consumption. No piece

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-08-10 Thread Leo Yan
On Tue, Jul 07, 2015 at 07:24:21PM +0100, Morten Rasmussen wrote: > From: Michael Turquette > > Scheduler-driven cpu frequency selection is desirable as part of the > on-going effort to make the scheduler better aware of energy > consumption. No piece of the Linux kernel has a better view of the

Re: [RFCv5 PATCH 38/46] sched: scheduler-driven cpu frequency selection

2015-07-08 Thread Michael Turquette
Quoting Morten Rasmussen (2015-07-07 11:24:21) > From: Michael Turquette > > Scheduler-driven cpu frequency selection is desirable as part of the > on-going effort to make the scheduler better aware of energy > consumption. No piece of the Linux kernel has a better view of the > factors that aff