Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752984Ab2HVLf1 (ORCPT ); Wed, 22 Aug 2012 07:35:27 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:45654 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750805Ab2HVLfY (ORCPT ); Wed, 22 Aug 2012 07:35:24 -0400 Date: Wed, 22 Aug 2012 12:35:08 +0100 From: Matthew Garrett To: Ingo Molnar Cc: Arjan van de Ven , Peter Zijlstra , Alex Shi , Suresh Siddha , vincent.guittot@linaro.org, svaidy@linux.vnet.ibm.com, Andrew Morton , Linus Torvalds , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Paul Turner Subject: Re: [discussion]sched: a rough proposal to enable power saving in scheduler Message-ID: <20120822113508.GA19152@srcf.ucam.org> References: <20120820181651.GA737@srcf.ucam.org> <20120821094203.GB12385@gmail.com> <20120821113951.GA22436@srcf.ucam.org> <20120821151910.GA5359@gmail.com> <20120821152828.GB28241@srcf.ucam.org> <20120821155908.GA5499@gmail.com> <20120821161324.GA29665@srcf.ucam.org> <20120821182346.GA7325@gmail.com> <20120821183414.GA436@srcf.ucam.org> <20120822091013.GB23336@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120822091013.GB23336@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1277 Lines: 32 On Wed, Aug 22, 2012 at 11:10:13AM +0200, Ingo Molnar wrote: > > * Matthew Garrett wrote: > > > [...] > > > > Our power consumption is worse than under other operating > > systems is almost entirely because only one of our three GPU > > drivers implements any kind of useful power management. [...] > > ... and because our CPU frequency and C state selection logic is > doing pretty much the worst possible decisions (on x86 at > least). You have figures showing that our C state residence is worse than, say, Windows? Because my own testing says that we're way better at that. Could we be better? Sure. Is it why we're worse? No. > Regardless, you cannot possibly seriously suggest that because > there's even greater suckage elsewhere for some workloads we > should not even bother with improving the situation here. I'm enthusiastic about improving the scheduler's behaviour. I'm unenthusiastic about putting in automatic hacks related to AC state. -- Matthew Garrett | mjg59@srcf.ucam.org -- 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/