On Tuesday, July 18, 2017 12:35:52 PM Juri Lelli wrote:
> On 18/07/17 16:55, Viresh Kumar wrote:
> > On 18-07-17, 12:20, Juri Lelli wrote:
> > > Hi Viresh,
> > >
> > > On 18/07/17 10:24, Viresh Kumar wrote:
>
> [...]
>
> > >
> > > It actually belongs here, IMHO. We update other fields (util, ma
On 18/07/17 16:55, Viresh Kumar wrote:
> On 18-07-17, 12:20, Juri Lelli wrote:
> > Hi Viresh,
> >
> > On 18/07/17 10:24, Viresh Kumar wrote:
[...]
> >
> > It actually belongs here, IMHO. We update other fields (util, max,
> > flags)
>
> Yeah, because they have bigger roles and aren't specific
On 18-07-17, 12:20, Juri Lelli wrote:
> Hi Viresh,
>
> On 18/07/17 10:24, Viresh Kumar wrote:
> > sg_cpu->last_update is always updated right after we call
> > sugov_set_iowait_boost() and its better to update it from that routine
> > itself. This makes it more readable.
> >
> > Signed-off-by: Vi
Hi Viresh,
On 18/07/17 10:24, Viresh Kumar wrote:
> sg_cpu->last_update is always updated right after we call
> sugov_set_iowait_boost() and its better to update it from that routine
> itself. This makes it more readable.
>
> Signed-off-by: Viresh Kumar
> ---
> kernel/sched/cpufreq_schedutil.c
sg_cpu->last_update is always updated right after we call
sugov_set_iowait_boost() and its better to update it from that routine
itself. This makes it more readable.
Signed-off-by: Viresh Kumar
---
kernel/sched/cpufreq_schedutil.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -
5 matches
Mail list logo