From: Tony Lindgren <tony@atomide.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: vatsa@in.ibm.com, Nick Piggin <nickpiggin@yahoo.com.au>,
schwidefsky@de.ibm.com, jdike@addtoit.com,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] (How to) Let idle CPUs sleep
Date: Thu, 12 May 2005 09:16:37 -0700 [thread overview]
Message-ID: <20050512161636.GA15653@atomide.com> (raw)
In-Reply-To: <1115913679.20909.31.camel@mindpipe>
* Lee Revell <rlrevell@joe-job.com> [050512 09:05]:
> On Thu, 2005-05-12 at 14:16 +0530, Srivatsa Vaddagiri wrote:
> > On Wed, May 11, 2005 at 11:03:49AM -0700, Tony Lindgren wrote:
> > > Sorry to jump in late. For embedded stuff we should be able to skip
> > > ticks until something _really_ happens, like an interrupt.
> > >
> > > So we need to be able to skip ticks several seconds at a time. Ticks
> > > should be event driven. For embedded systems option B is really
> > > the only way to go to take advantage of the power savings.
> >
> > I don't know how sensitive embedded platforms are to load imbalance.
> > If they are not sensitive, then we could let the max time idle
> > cpus are allowed to sleep to be few seconds. That way, idle CPU
> > wakes up once in 3 or 4 seconds to check for imbalance and still
> > be able to save power for those 3/4 seconds that it sleeps.
>
> Not very. Embedded systems are usually UP so don't care at all. If an
> embedded system is SMP often it's because one CPU is dedicated to RT
> tasks, and this model will become less common as RT preemption allows
> you to do everything on a single processor.
Yes UP mostly & sounds like this only affects MP systems.
Although there is ARM MP support patches available.
I guess embedded MP systems may be used for multimedia
stuff eventually.
Tony
next prev parent reply other threads:[~2005-05-12 16:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 18:27 Srivatsa Vaddagiri
2005-05-08 3:50 ` Rusty Russell
2005-05-08 4:14 ` Nick Piggin
2005-05-08 12:19 ` Srivatsa Vaddagiri
2005-05-09 6:27 ` Nick Piggin
2005-05-12 8:38 ` Srivatsa Vaddagiri
2005-05-11 18:03 ` Tony Lindgren
2005-05-12 8:46 ` Srivatsa Vaddagiri
2005-05-12 16:01 ` Lee Revell
2005-05-12 16:16 ` Tony Lindgren [this message]
2005-05-12 16:28 ` Jesse Barnes
2005-05-12 17:12 ` Srivatsa Vaddagiri
2005-05-12 17:59 ` Jesse Barnes
2005-05-12 18:16 ` Tony Lindgren
2005-05-13 6:27 ` Srivatsa Vaddagiri
2005-05-12 18:08 ` Martin Schwidefsky
2005-05-12 18:21 ` Tony Lindgren
2005-05-13 6:23 ` Srivatsa Vaddagiri
2005-05-13 7:16 ` Nick Piggin
2005-05-13 8:04 ` Ingo Molnar
2005-05-13 8:27 ` Nick Piggin
2005-05-13 9:19 ` Srivatsa Vaddagiri
2005-05-13 9:33 ` Nick Piggin
2005-05-12 21:16 ` George Anzinger
2005-05-12 21:35 ` Jesse Barnes
2005-05-12 22:15 ` George Anzinger
2005-05-13 0:43 ` Jesse Barnes
2005-05-13 6:31 ` Srivatsa Vaddagiri
2005-06-30 12:47 ` Srivatsa Vaddagiri
2005-07-06 17:31 ` Srivatsa Vaddagiri
2005-05-08 10:13 ` Arjan van de Ven
2005-05-08 13:33 ` Andi Kleen
2005-05-08 13:44 ` Arjan van de Ven
2005-05-08 14:53 ` Andi Kleen
2005-05-08 13:31 ` Andi Kleen
2005-05-08 15:26 ` Srivatsa Vaddagiri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050512161636.GA15653@atomide.com \
--to=tony@atomide.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=rlrevell@joe-job.com \
--cc=schwidefsky@de.ibm.com \
--cc=vatsa@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome