Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753399AbaJCOvY (ORCPT ); Fri, 3 Oct 2014 10:51:24 -0400 Received: from mail-ob0-f176.google.com ([209.85.214.176]:34244 "EHLO mail-ob0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752541AbaJCOvV (ORCPT ); Fri, 3 Oct 2014 10:51:21 -0400 MIME-Version: 1.0 In-Reply-To: <20141003143634.GL2849@worktop.programming.kicks-ass.net> References: <1411488485-10025-1-git-send-email-vincent.guittot@linaro.org> <1411488485-10025-4-git-send-email-vincent.guittot@linaro.org> <20141003143634.GL2849@worktop.programming.kicks-ass.net> From: Vincent Guittot Date: Fri, 3 Oct 2014 16:51:01 +0200 Message-ID: Subject: Re: [PATCH v6 3/6] sched: add utilization_avg_contrib To: Peter Zijlstra Cc: Ingo Molnar , linux-kernel , Preeti U Murthy , Russell King - ARM Linux , LAK , Rik van Riel , Morten Rasmussen , Mike Galbraith , Nicolas Pitre , "linaro-kernel@lists.linaro.org" , Daniel Lezcano , Dietmar Eggemann , Paul Turner , Benjamin Segall Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3 October 2014 16:36, Peter Zijlstra wrote: > >> + * utilization_load_avg is the sum of the average running time of the >> + * sched_entities on the rq. >> */ > > So I think there was some talk about a blocked_utilization thingy, which > would track the avg running time of the tasks currently asleep, right? > yes. Do you mean that we should anticipate and rename utilization_load_avg into utilization_runnable_avg to make space for a utilization_blocked_avg that could be added in future ? >> + unsigned long runnable_load_avg, blocked_load_avg, utilization_load_avg; >> atomic64_t decay_counter; >> u64 last_decay; >> atomic_long_t removed_load; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/