From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: george@mvista.com, Jesse Barnes <jesse.barnes@intel.com>,
Tony Lindgren <tony@atomide.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
Subject: Re: [RFC] (How to) Let idle CPUs sleep
Date: Fri, 13 May 2005 12:01:13 +0530 [thread overview]
Message-ID: <20050513063113.GF23705@in.ibm.com> (raw)
In-Reply-To: <200505121743.46313.jbarnes@virtuousgeek.org>
On Thu, May 12, 2005 at 05:43:46PM -0700, Jesse Barnes wrote:
> But in this case you probably want it to, so it can rebalance tasks to
> the CPU that just woke up.
Usually the sleeping idle CPU is sent a resched IPI, which will cause it to
call schedule or idle_balance_retry/rebalance_tick (ref: my earlier patch) to
find out if it has do a load balance.
--
Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017
next prev parent reply other threads:[~2005-05-13 6:31 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
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 [this message]
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=20050513063113.GF23705@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=george@mvista.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jdike@addtoit.com \
--cc=jesse.barnes@intel.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=tony@atomide.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.