From: "Gregory Haskins" <ghaskins@novell.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: <rostedt@goodmis.org>, <peterz@infradead.org>, <npiggin@suse.de>,
<linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 0/3] sched: newidle and RT wake-buddy fixes
Date: Mon, 30 Jun 2008 11:16:55 -0600 [thread overview]
Message-ID: <4868DCC7.BA47.005A.0@novell.com> (raw)
In-Reply-To: <20080630131511.GA7506@elte.hu>
>>> On Mon, Jun 30, 2008 at 9:15 AM, in message <20080630131511.GA7506@elte.hu>,
Ingo Molnar <mingo@elte.hu> wrote:
> * Gregory Haskins <ghaskins@novell.com> wrote:
>
>> Hi Ingo,
>> The following patches apply to linux-tip/sched/devel and enhance the
>> performance of the kernel (specifically in PREEMPT_RT, though they do
>> not regress mainline performance as far as I can tell). They offer
>> somewhere between 50-100% speedups in netperf performance, depending
>> on the test.
>
> -tip testing found this boot hang:
I may have found the issue: It looks like the hunk that initially disables interrupts in load_balance_newidle() was inadvertently applied to load_balance() instead during the
merge to linux-tip. If you fold the following patch into my original patch, it should set
things right again.
-----
sched: fix merge problem with newidle enhancement patch
From: Gregory Haskins <ghaskins@novell.com>
commit cc8160c56843201891766660e3816d2e546c1b17 introduces a locking
enhancement for newidle. However, one hunk misapplied to load_balance
instead of load_balance_newidle. This fixes the issue.
Signed-off-by: Gregory Haskins <ghaskins@novell.com>
---
kernel/sched.c | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index f35d73c..f36406f 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -3459,15 +3459,6 @@ static int load_balance(int this_cpu, struct rq *this_rq,
cpus_setall(*cpus);
- schedstat_inc(sd, lb_count[CPU_NEWLY_IDLE]);
-
- /*
- * We are in a preempt-disabled section, so dropping the lock/irq
- * here simply means that other cores may acquire the lock,
- * and interrupts may occur.
- */
- spin_unlock_irq(&this_rq->lock);
-
/*
* When power savings policy is enabled for the parent domain, idle
* sibling can pick up load irrespective of busy siblings. In this case,
@@ -3630,6 +3621,15 @@ load_balance_newidle(int this_cpu, struct rq *this_rq, struct sched_domain *sd,
cpus_setall(*cpus);
+ schedstat_inc(sd, lb_count[CPU_NEWLY_IDLE]);
+
+ /*
+ * We are in a preempt-disabled section, so dropping the lock/irq
+ * here simply means that other cores may acquire the lock,
+ * and interrupts may occur.
+ */
+ spin_unlock_irq(&this_rq->lock);
+
/*
* When power savings policy is enabled for the parent domain, idle
* sibling can pick up load irrespective of busy siblings. In this case,
next prev parent reply other threads:[~2008-06-30 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 20:29 [PATCH 0/3] sched: newidle and RT wake-buddy fixes Gregory Haskins
2008-06-27 20:29 ` [PATCH 1/3] sched: enable interrupts and drop rq-lock during newidle balancing Gregory Haskins
2008-06-27 20:29 ` [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over Gregory Haskins
2008-07-08 5:00 ` Nick Piggin
2008-07-08 12:37 ` Gregory Haskins
2008-07-09 8:09 ` Nick Piggin
2008-07-09 10:53 ` Gregory Haskins
2008-07-09 11:17 ` Nick Piggin
2008-07-09 11:53 ` Gregory Haskins
2008-06-27 20:30 ` [PATCH 3/3] sched: add avg-overlap support to RT tasks Gregory Haskins
2008-06-27 20:51 ` [PATCH 0/3] sched: newidle and RT wake-buddy fixes Peter Zijlstra
2008-06-30 12:56 ` Ingo Molnar
2008-06-30 13:15 ` Ingo Molnar
2008-06-30 11:20 ` Gregory Haskins
2008-06-30 14:41 ` Gregory Haskins
2008-06-30 15:01 ` Steven Rostedt
2008-06-30 17:16 ` Gregory Haskins [this message]
2008-06-30 18:10 ` Ingo Molnar
2008-07-03 14:41 ` Ingo Molnar
2008-07-03 15:12 ` Ingo Molnar
2008-07-08 12:38 ` Gregory Haskins
2008-07-08 16:45 ` Gregory Haskins
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=4868DCC7.BA47.005A.0@novell.com \
--to=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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