From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756031AbcHBW0Q (ORCPT ); Tue, 2 Aug 2016 18:26:16 -0400 Received: from mail-pa0-f54.google.com ([209.85.220.54]:34482 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753011AbcHBW0E (ORCPT ); Tue, 2 Aug 2016 18:26:04 -0400 From: Steve Muckle X-Google-Original-From: Steve Muckle Date: Tue, 2 Aug 2016 15:02:45 -0700 To: "Rafael J. Wysocki" Cc: Steve Muckle , "Rafael J. Wysocki" , Linux PM list , Peter Zijlstra , Srinivas Pandruvada , Viresh Kumar , Linux Kernel Mailing List , Juri Lelli , Ingo Molnar Subject: Re: [RFC][PATCH 5/7] cpufreq / sched: UUF_IO flag to indicate iowait condition Message-ID: <20160802220245.GA26555@graphite.smuckle.net> References: <3752826.3sXAQIvcIA@vostro.rjw.lan> <3009663.9YcxTKseiO@vostro.rjw.lan> <20160802012209.GB9332@graphite.smuckle.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 02, 2016 at 03:37:02AM +0200, Rafael J. Wysocki wrote: > On Tue, Aug 2, 2016 at 3:22 AM, Steve Muckle wrote: > > On Mon, Aug 01, 2016 at 01:37:23AM +0200, Rafael J. Wysocki wrote: > > ... > >> For this purpose, define a new cpufreq_update_util() flag > >> UUF_IO and modify enqueue_task_fair() to pass that flag to > >> cpufreq_update_util() in the in_iowait case. That generally > >> requires cpufreq_update_util() to be called directly from there, > >> because update_load_avg() is not likely to be invoked in that > >> case. > > > > I didn't follow why the cpufreq hook won't likely be called if > > in_iowait is set? AFAICS update_load_avg() gets called in the second loop > > and calls update_cfs_rq_load_avg (triggers the hook). > > In practice it turns out that in the majority of cases when in_iowait > is set the second loop will not run. My understanding of enqueue_task_fair() is that the first loop walks up the portion of the sched_entity hierarchy that needs to be enqueued, and the second loop updates the rest of the hierarchy that was already enqueued. Even if the se corresponding to the root cfs_rq needs to be enqueued (meaning the whole hierarchy is traversed in the first loop and the second loop does nothing), enqueue_entity() on the root cfs_rq should result in the cpufreq hook being called, via enqueue_entity() -> enqueue_entity_load_avg() -> update_cfs_rq_load_avg(). I'll keep looking to see if I've misunderstood something in here. thanks, Steve