[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 5 May 2017 09:26:35 -0400
From: Tejun Heo <tj@...nel.org>
To: Dietmar Eggemann <dietmar.eggemann@....com>
Cc: Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Mike Galbraith <efault@....de>, Paul Turner <pjt@...gle.com>,
Chris Mason <clm@...com>, kernel-team@...com
Subject: Re: [PATCH 2/3] sched/fair: Add load_weight->runnable_load_{sum|avg}
On Fri, May 05, 2017 at 02:22:05PM +0100, Dietmar Eggemann wrote:
> Hi Tejun,
>
> On 04/05/17 21:29, Tejun Heo wrote:
> > Currently, runnable_load_avg, which represents the portion of load avg
> > only from tasks which are currently active, is tracked by cfs_rq but
> > not by sched_entity. We want to propagate runnable_load_avg of a
> > nested cfs_rq without affecting load_avg propagation. To implement an
> > equivalent propagation channel, sched_entity needs to track
> > runnable_load_avg too.
> >
> > This patch moves cfs_rq->runnable_load_{sum|avg} into struct
> > load_weight which is already used to track load_avg and shared by both
> > cfs_rq and sched_entity.
> >
> > This patch only changes where runnable_load_{sum|avg} are located and
> > doesn't cause any actual behavior changes. The fields are still only
> > used for cfs_rqs.
>
> This one doesn't apply cleanly on tip/sched/core. There has been a lot
> of changes in the actual PELT code.
The patches are on top of v4.11 as noted in the head message.
Thanks.
--
tejun
Powered by blists - more mailing lists