From: Christoph Lameter <clameter@sgi.com>
To: akpm@osdl.org
Cc: Peter Williams <pwil3058@bigpond.net.au>,
linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
Christoph Lameter <clameter@sgi.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Ingo Molnar <mingo@elte.hu>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>
Subject: [PATCH 7/7] Call tasklet less frequently
Date: Fri, 27 Oct 2006 19:41:48 -0700 (PDT) [thread overview]
Message-ID: <20061028024148.10809.19537.sendpatchset@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20061028024112.10809.15841.sendpatchset@schroedinger.engr.sgi.com>
Schedule load balance tasklet less frequently
We schedule the tasklet before this patch always with the value in
sd->interval. However, if the queue is busy then it is sufficient
to schedule the tasklet with sd->interval*busy_factor.
So we modify the calculation of the next time to balance by taking
the interval added to last_balance again. This is only the
right value if the idle/busy situation continues as is.
There are two potential trouble spots:
- If the queue was idle and now gets busy then we call rebalance
early. However, that is not a problem because we will then use
the longer interval for the next period.
- If the queue was busy and becomes idle then we potentially
wait too long before rebalancing. However, when the task
goes idle then idle_balance is called. We add another calculation
of the next balance time based on sd->interval in idle_balance
so that we will rebalance soon.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
Index: linux-2.6.19-rc3/kernel/sched.c
===================================================================
--- linux-2.6.19-rc3.orig/kernel/sched.c 2006-10-27 20:36:37.269918493 -0500
+++ linux-2.6.19-rc3/kernel/sched.c 2006-10-27 20:41:10.765080822 -0500
@@ -2757,14 +2757,26 @@ out_balanced:
static void idle_balance(int this_cpu, struct rq *this_rq)
{
struct sched_domain *sd;
+ int pulled_task = 0;
+ unsigned long next_balance = jiffies + 60 * HZ;
for_each_domain(this_cpu, sd) {
if (sd->flags & SD_BALANCE_NEWIDLE) {
/* If we've pulled tasks over stop searching: */
- if (load_balance_newidle(this_cpu, this_rq, sd))
+ pulled_task = load_balance_newidle(this_cpu,
+ this_rq, sd);
+ next_balance = min(next_balance,
+ sd->last_balance + sd->balance_interval);
+ if (pulled_task)
break;
}
}
+ if (!pulled_task)
+ /*
+ * We are going idle. next_balance may be set based on
+ * a busy processor. So reset next_balance.
+ */
+ this_rq->next_balance = next_balance;
}
/*
@@ -2889,8 +2901,16 @@ static void rebalance_domains(unsigned l
}
sd->last_balance += interval;
}
+ /*
+ * Calculate the next balancing point assuming that
+ * the idle state does not change. If we are idle and then
+ * start running a process then this will be recalculated.
+ * If we are running a process and then become idle
+ * then idle_balance will reset next_balance so that we
+ * rebalance earlier.
+ */
next_balance = min(next_balance,
- sd->last_balance + sd->balance_interval);
+ sd->last_balance + interval);
}
this_rq->next_balance = next_balance;
}
next prev parent reply other threads:[~2006-10-28 2:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 2:41 [PATCH 0/7] sched_domain balancing via tasklet V2 Christoph Lameter
2006-10-28 2:41 ` [PATCH 1/7] Avoid taking rq lock in wake_priority_sleeper Christoph Lameter
2006-10-28 2:41 ` [PATCH 2/7] Disable interrupts for locking in load_balance() Christoph Lameter
2006-10-28 2:41 ` [PATCH 3/7] Extract load calculation from rebalance_tick Christoph Lameter
2006-10-28 2:41 ` [PATCH 4/7] Stagger load balancing in build_sched_domains Christoph Lameter
2006-10-28 2:41 ` [PATCH 5/7] Move idle stat calculation into rebalance_tick() Christoph Lameter
2006-10-28 17:57 ` Siddha, Suresh B
2006-10-29 1:05 ` Christoph Lameter
2006-10-28 2:41 ` [PATCH 6/7] Use tasklet to call balancing Christoph Lameter
2006-10-28 2:41 ` Christoph Lameter [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-03 20:46 [PATCH 0/7] sched_domain balancing via tasklet V3 Christoph Lameter
2006-11-03 20:47 ` [PATCH 7/7] Call tasklet less frequently Christoph Lameter
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=20061028024148.10809.19537.sendpatchset@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
--cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox