From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: george@mvista.com, mingo@elte.hu,
high-res-timers-discourse@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: VST and Sched Load Balance
Date: Thu, 7 Apr 2005 19:30:40 +0530 [thread overview]
Message-ID: <20050407140040.GD17268@in.ibm.com> (raw)
In-Reply-To: <425530AB.90605@yahoo.com.au>
On Thu, Apr 07, 2005 at 11:07:55PM +1000, Nick Piggin wrote:
> 3. This is exactly one of the situations that the balancing backoff code
> was designed for. Can you just schedule interrupts to fire when the
> next balance interval has passed? This may require some adjustments to
> the backoff code in order to get good powersaving, but it would be the
> cleanest approach from the scheduler's point of view.
Hmm ..I guess we could restrict the max time a idle CPU will sleep taking
into account its balance interval. But whatever heuristics we follow to
maximize balance_interval of about-to-sleep idle CPU, don't we still run the
risk of idle cpu being woken up and going immediately back to sleep (because
there was no imbalance)?
Moreover we may be greatly reducing the amount of time a CPU is allowed to
sleep this way ...
--
Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017
next prev parent reply other threads:[~2005-04-07 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 12:46 VST and Sched Load Balance Srivatsa Vaddagiri
2005-04-07 13:07 ` Nick Piggin
2005-04-07 14:00 ` Srivatsa Vaddagiri [this message]
2005-04-07 14:06 ` Nick Piggin
2005-05-05 14:39 ` Srivatsa Vaddagiri
2005-05-05 14:52 ` Nick Piggin
2005-05-05 16:15 ` Srivatsa Vaddagiri
2005-04-07 15:10 ` Ingo Molnar
2005-04-08 5:34 ` Srivatsa Vaddagiri
2005-04-08 6:33 ` Nick Piggin
2005-04-19 16:07 ` Nish Aravamudan
2005-04-20 9:11 ` Srivatsa Vaddagiri
-- strict thread matches above, loose matches on Subject: below --
2005-04-07 16:25 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=20050407140040.GD17268@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=george@mvista.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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