From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Williams <pwil3058@bigpond.net.au>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] sched_tick with interrupts enabled
Date: Wed, 18 Oct 2006 19:19:00 -0700 [thread overview]
Message-ID: <20061018191900.D26521@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610181457130.30795@schroedinger.engr.sgi.com>; from clameter@sgi.com on Wed, Oct 18, 2006 at 02:59:07PM -0700
On Wed, Oct 18, 2006 at 02:59:07PM -0700, Christoph Lameter wrote:
> load_balancing has the potential of running for some time if f.e.
> sched_domains for a system with 1024 processors have to be balanced.
> We currently do all of that with interrupts disabled. So we may be unable
> to service interrupts for some time. Most of that time is potentially
> spend in rebalance_tick.
Did you see an issue because of this or just theoretical?
> +static void rebalance_tick(unsigned long dummy)
> {
> + int this_cpu = smp_processor_id();
> + struct rq *this_rq = cpu_rq(this_cpu);
> + enum idle_type idle;
> unsigned long this_load, interval, j = cpu_offset(this_cpu);
> struct sched_domain *sd;
> int i, scale;
>
> + idle = (current == this_rq->idle) ? SCHED_IDLE : NOT_IDLE;
We need to add nr_running check too, to determine if we want to do
idle/not-idle balancing. This is in the context of wake_priority_sleeper()
thanks,
suresh
next prev parent reply other threads:[~2006-10-19 2:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 17:04 [RFC] sched_tick with interrupts enabled Christoph Lameter
2006-10-18 17:21 ` Nick Piggin
2006-10-18 18:01 ` Christoph Lameter
2006-10-18 18:09 ` Nick Piggin
2006-10-18 18:48 ` Christoph Lameter
2006-10-18 19:14 ` Nick Piggin
2006-10-18 21:59 ` Christoph Lameter
2006-10-19 2:19 ` Siddha, Suresh B [this message]
2006-10-19 10:16 ` KAMEZAWA Hiroyuki
2006-10-19 15:50 ` Christoph Lameter
2006-10-19 20:40 ` Siddha, Suresh B
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=20061018191900.D26521@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.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