From: Tony Lindgren <tony@atomide.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: vatsa@in.ibm.com, Lee Revell <rlrevell@joe-job.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
schwidefsky@de.ibm.com, jdike@addtoit.com,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, george@mvista.com
Subject: Re: [RFC] (How to) Let idle CPUs sleep
Date: Thu, 12 May 2005 11:16:45 -0700 [thread overview]
Message-ID: <20050512181644.GD15812@atomide.com> (raw)
In-Reply-To: <4283999F.8080609@virtuousgeek.org>
* Jesse Barnes <jbarnes@virtuousgeek.org> [050512 11:01]:
> Srivatsa Vaddagiri wrote:
>
> >Even if we were to go for this tickless design, the fundamental question
> >remains: who wakes up the (sleeping) idle CPU upon a imbalance? Does some
> >other
> >(busy) CPU wake it up (which makes the implementation complex) or the idle
> >CPU checks imbalance itself at periodic intervals (which restricts the
> >amount of
> >time a idle CPU may sleep).
> >
> >
> Waking it up at fork or exec time might be doable, and having a busy CPU
> wake up other CPUs wouldn't add too much complexity, would it?
At least then it would be event driven rather than polling approach.
Tony
next prev parent reply other threads:[~2005-05-12 18:17 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 18:27 [uml-devel] [RFC] (How to) Let idle CPUs sleep Srivatsa Vaddagiri
2005-05-07 18:27 ` Srivatsa Vaddagiri
2005-05-08 3:50 ` [uml-devel] " Rusty Russell
2005-05-08 3:50 ` Rusty Russell
2005-05-08 4:14 ` [uml-devel] " Nick Piggin
2005-05-08 4:14 ` Nick Piggin
2005-05-08 12:19 ` [uml-devel] " Srivatsa Vaddagiri
2005-05-08 12:19 ` Srivatsa Vaddagiri
2005-05-09 6:27 ` [uml-devel] " Nick Piggin
2005-05-09 6:27 ` Nick Piggin
2005-05-12 8:38 ` Srivatsa Vaddagiri
2005-05-11 18:03 ` [uml-devel] " Tony Lindgren
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
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 [this message]
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 ` [uml-devel] " Arjan van de Ven
2005-05-08 10:13 ` Arjan van de Ven
2005-05-08 13:33 ` [uml-devel] " Andi Kleen
2005-05-08 13:33 ` Andi Kleen
2005-05-08 13:44 ` [uml-devel] " Arjan van de Ven
2005-05-08 13:44 ` Arjan van de Ven
2005-05-08 14:53 ` [uml-devel] " Andi Kleen
2005-05-08 14:53 ` Andi Kleen
2005-05-08 13:31 ` [uml-devel] " Andi Kleen
2005-05-08 13:31 ` Andi Kleen
2005-05-08 15:26 ` [uml-devel] " Srivatsa Vaddagiri
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=20050512181644.GD15812@atomide.com \
--to=tony@atomide.com \
--cc=george@mvista.com \
--cc=jbarnes@virtuousgeek.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.