Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757369AbbKFTL1 (ORCPT ); Fri, 6 Nov 2015 14:11:27 -0500 Received: from mga11.intel.com ([192.55.52.93]:38100 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751046AbbKFTLZ (ORCPT ); Fri, 6 Nov 2015 14:11:25 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,253,1444719600"; d="scan'208";a="679919212" Date: Fri, 6 Nov 2015 11:10:30 -0800 From: Jacob Pan To: Dietmar Eggemann Cc: Peter Zijlstra , Eduardo Valentin , Thomas Gleixner , LKML , Arjan van de Ven , Paul Turner , Len Brown , Srinivas Pandruvada , Tim Chen , Andi Kleen , Rafael Wysocki , jacob.jun.pan@linux.intel.com Subject: Re: [RFC PATCH 0/3] CFS idle injection Message-ID: <20151106111030.6cc5a032@icelake> In-Reply-To: <563CF1A9.8030700@arm.com> References: <1446509428-5616-1-git-send-email-jacob.jun.pan@linux.intel.com> <20151104060654.GC8850@localhost.localdomain> <20151104085830.010e69f8@yairi> <20151105101218.GB3604@twins.programming.kicks-ass.net> <563CF1A9.8030700@arm.com> Organization: OTC X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1534 Lines: 37 On Fri, 6 Nov 2015 18:30:01 +0000 Dietmar Eggemann wrote: > On 05/11/15 10:12, Peter Zijlstra wrote: > > > > People, trim your emails! > > > > On Wed, Nov 04, 2015 at 08:58:30AM -0800, Jacob Pan wrote: > > > >>> I also like #2 too. Specially now that it is not limited to a > >>> specific platform. One question though, could you still keep the > >>> cooling device support of it? In some systems, it might make > >>> sense to enable / disable idle injections based on temperature. > > > >> One of the key difference between 1 and 2 is that #2 is open loop > >> control, since we don't have CPU c-states info baked into > >> scheduler. > > > > _yet_, there's people working on that. The whole power aware > > scheduling stuff needs that. > > Isn't the idle state information (rq->idle_state) already used in > find_idlest_cpu()? > > What we use in energy aware scheduling is quite similar but since > we're interested in the index information of the c-state (to access > the right element of the idle_state vectors of the energy model, we > added rq->idle_state_idx. > what i am interested is not per cpu idle state but rather at the package level or domain. It must be an indication for the overlapped idle time. Usually has to come from HW counters. -- 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/