[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160815142342.GV6879@twins.programming.kicks-ass.net>
Date: Mon, 15 Aug 2016 16:23:42 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Morten Rasmussen <morten.rasmussen@....com>
Cc: mingo@...hat.com, dietmar.eggemann@....com, yuyang.du@...el.com,
vincent.guittot@...aro.org, mgalbraith@...e.de,
sgurrappadi@...dia.com, freedom.tan@...iatek.com,
keita.kobayashi.ym@...esas.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 10/13] sched/fair: Compute task/cpu utilization at
wake-up more correctly
On Mon, Jul 25, 2016 at 02:34:27PM +0100, Morten Rasmussen wrote:
> To solve this problem, this patch introduces task_util_wake() which
> computes the decayed task utilization based on the last update of the
> previous cpu's last load-tracking update. It is done without having to
> take the rq lock, similar to how it is done in remove_entity_load_avg().
But unlike that function, it doesn't actually use __update_load_avg().
Why not?
Powered by blists - more mailing lists