From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753547AbdEEN0p (ORCPT ); Fri, 5 May 2017 09:26:45 -0400 Received: from mail-qk0-f194.google.com ([209.85.220.194]:33584 "EHLO mail-qk0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752572AbdEEN0n (ORCPT ); Fri, 5 May 2017 09:26:43 -0400 Date: Fri, 5 May 2017 09:26:35 -0400 From: Tejun Heo To: Dietmar Eggemann Cc: Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org, Linus Torvalds , Vincent Guittot , Mike Galbraith , Paul Turner , Chris Mason , kernel-team@fb.com Subject: Re: [PATCH 2/3] sched/fair: Add load_weight->runnable_load_{sum|avg} Message-ID: <20170505132635.GB8936@wtj.duckdns.org> References: <20170504202838.GA2647@htj.duckdns.org> <20170504202948.GC2647@htj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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