On Fri, 4 Jun 2010, Ingo Molnar wrote:
What you say is absolutely true, hence this would be driven via sched_tick()
+
TIF notifiers - i.e. only ever treat user-mode tasks as 'idle-able'. This can
be done with no overhead to the regular fastpaths.
The TIF notifier would be the one
On Thu, 3 Jun 2010, Linus Torvalds wrote:
so I'd like to see the opportunistc suspend thing think about CPU
offlining
Side note: one reason for me being somewhat interested in the CPU
offlining is that I think the Android kind of opportunistic suspend is
_not_ likely something I'd like
Kevin Hilman wrote:
Mike Chan m...@android.com writes:
On Fri, May 21, 2010 at 9:47 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Mike Chan m...@android.com writes:
I'm not sure if this has been discussed, yet but since it seems that
the resource framework will not be making
On Thu, 3 Jun 2010 19:26:50 -0700 (PDT)
Linus Torvalds torva...@linux-foundation.org wrote:
If the system is idle (or almost idle) for long times, I would
heartily recommend actively shutting down unused cores. Some CPU's
are hopefully smart enough to not even need that kind of software
On Thu, Jun 3, 2010 at 7:16 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Fri, 4 Jun 2010, Ingo Molnar wrote:
What you say is absolutely true, hence this would be driven via sched_tick()
+
TIF notifiers - i.e. only ever treat user-mode tasks as 'idle-able'. This can
be done
On Fri, 4 Jun 2010 01:23:02 +0200
Ingo Molnar mi...@elte.hu wrote:
Btw., i'd like to summarize the scheduler based suspend scheme proposed by
Thomas Gleixner, Peter Zijlstra and myself. I found no good summary of it in
the big thread, and there are also new elements of the proposal:
Hi
I
On Thu, 3 Jun 2010, Arjan van de Ven wrote:
And because there's then no power saving (but a performance cost), it's
actually a negative for battery life/total energy.
Including the UP optimizations we do (ie lock prefix removal)? It's
possible that I'm just biased by benchmarks, and it's
On Thu, Jun 3, 2010 at 4:23 PM, Ingo Molnar mi...@elte.hu wrote:
...
- Controlled auto-suspend: drivers (such as input) could on wakeup
automatically set the 'minimum wakeup latency' value of wakee tasks to a
lower value. This automatically prevents another auto-suspend in the near
101 - 108 of 108 matches
Mail list logo
