[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51E5ADC5.9010105@linux.intel.com>
Date: Tue, 16 Jul 2013 13:32:05 -0700
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: Morten Rasmussen <morten.rasmussen@....com>, mingo@...nel.org,
vincent.guittot@...aro.org, preeti@...ux.vnet.ibm.com,
alex.shi@...el.com, efault@....de, pjt@...gle.com,
len.brown@...el.com, corbet@....net, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, tglx@...utronix.de,
catalin.marinas@....com, linux-kernel@...r.kernel.org,
linaro-kernel@...ts.linaro.org
Subject: Re: [RFC][PATCH 0/9] sched: Power scheduler design proposal
On 7/16/2013 1:17 PM, Peter Zijlstra wrote:
> On Tue, Jul 16, 2013 at 12:57:34PM -0700, Arjan van de Ven wrote:
>> then the question of how much remaining capacity; this is a hard one, and not just
>> for Intel. Almost all mobile devices today are thermally constrained, ARM and Intel
>> alike (at least the higher performance ones)... the curse of wanting very thin and light
>> phones that are made of thermally isolating plastic (so that radio waves can go through)
>> and have a nice and bright screen...
>
> Right, so we might need to track a !idle avg over the thermal domain to
> guestimate the head-room and inter-cpu relations.
btw one thing to realize is that many of the thermal limits in mobile devices don't have the CPU cores
as the primary reason.
Other components on the board (screens, modems etc) as well as the GPU likely impact
this at least as much as actual cpu usage does.
It's usually just that the CPU is the easiest to control down,
so that tends to be the first one impacted.
--
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