From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: mingo@elte.hu, george@mvista.com,
high-res-timers-discourse@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: VST and Sched Load Balance
Date: Thu, 5 May 2005 21:45:13 +0530 [thread overview]
Message-ID: <20050505161513.GA20217@in.ibm.com> (raw)
In-Reply-To: <427A3340.1020305@yahoo.com.au>
On Fri, May 06, 2005 at 12:52:48AM +1000, Nick Piggin wrote:
> Well, there are a lot of ifs and buts. Some domains won't implement
> fork balancing, others won't do newidle balancing, wake balancing,
> wake to idle, etc etc.
Good point. I had somehow assumed that these are true for all domains.
My bad ..
>
> I think my idea of allowing max_interval to be extended to a
> sufficiently large value if one CPU goes idle, and shutting off all
> CPU's rebalancing completely if no tasks are running for some time
> should cater to both hypervisor images and power saving concerns.
Maybe we should check with virtual machine folks on this. Will
check with UML and S390 folks tomorrow.
> >A possible patch for B follows below:
> >
>
> Yeah something like that should do it.
Ok ..thanks. Will include this patch in the final
load-balance-fix-for-no-hz-idle-cpus's patch!
--
Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017
next prev parent reply other threads:[~2005-05-05 16:14 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
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 [this message]
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=20050505161513.GA20217@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