[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1242225402.26820.23.camel@twins>
Date: Wed, 13 May 2009 16:36:42 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Andi Kleen <andi@...stfloor.org>
Cc: Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Suresh B Siddha <suresh.b.siddha@...el.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
Arjan van de Ven <arjan@...radead.org>,
Ingo Molnar <mingo@...e.hu>,
Dipankar Sarma <dipankar@...ibm.com>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Vatsa <vatsa@...ux.vnet.ibm.com>,
Gautham R Shenoy <ego@...ibm.com>,
Gregory Haskins <gregory.haskins@...il.com>,
Mike Galbraith <efault@....de>,
Thomas Gleixner <tglx@...utronix.de>,
Arun Bharadwaj <arun@...ux.vnet.ibm.com>
Subject: Re: [RFC PATCH v2 0/2] Saving power by cpu evacuation
sched_max_capacity_pct=n
On Wed, 2009-05-13 at 16:35 +0200, Andi Kleen wrote:
> On Wed, May 13, 2009 at 06:41:00PM +0530, Vaidyanathan Srinivasan wrote:
> > * Using sched_mc=3,4,5 to evacuate 1,2,4 cores is completely
> > non-intuitive and broken interface. Ingo wanted to see if we can
> > model a global percentile tunable that would map to core throttling.
>
> I have one request. CPU throttling is already a very well established
> term in the x86 world, refering to thermal throttling when the CPU
> overheats. This is implemented by ACPI and the CPU. It's always
> a very bad thing that should be avoided at all costs.
Its about avoiding that.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists