public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 08:41:05 -0600	[thread overview]
Message-ID: <4868B841.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:

Ok, I dug in a little bit here.  I haven't verified this out yet, but I think the problem is that
your config is PREEMPT_VOLUNTARY which NOPs the preempt_disable() in schedule() that
I rely on to allow the lock to be dropped.  (Doh!)

One way I can fix this is to fixup the newidle() code to only play the irq dropping tricks
ifdef CONFIG_PREEMPT == TRUE.  Does this sound reasonable, or is there a better way
to address this?

-Greg

> 
>  Linux version 2.6.26-rc8-tip (mingo@dione) (gcc version 4.2.3) #12917 
>  SMP Mon Jun 30 15:06:32 CEST 2008
>  [...]
>  CPU 1/1 -> Node 0
>  CPU: Physical Processor ID: 0
>  CPU: Processor Core ID: 1
>  CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
>  Brought up 2 CPUs
>  Total of 2 processors activated (8041.15 BogoMIPS).
>  [ hard hang ]
> 
> with this config:
> 
>   http://redhat.com/~mingo/misc/config-Mon_Jun_30_14_54_19_CEST_2008.bad
> 
> full bootlog:
> 
>   http://redhat.com/~mingo/misc/hang-Mon_Jun_30_14_54_19_CEST_2008.bad
> 
> it should continue with this bootup sequence:
> 
>   calling  net_ns_init+0x0/0x1a0
>   net_namespace: 376 bytes
>   initcall net_ns_init+0x0/0x1a0 returned 0 after 0 msecs
>   calling  init_smp_flush+0x0/0x60
> 
> i've bisected it down to:
> 
> --------------
> | commit cc8160c56843201891766660e3816d2e546c1b17
> | Author: Gregory Haskins <ghaskins@novell.com>
> | Date:   Fri Jun 27 14:29:50 2008 -0600
> |
> |     sched: enable interrupts and drop rq-lock during newidle balancing
> --------------
> 
> so i've reverted that change for now.
> 
> 	Ingo



  parent reply	other threads:[~2008-06-30 14:48 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 [this message]
2008-06-30 15:01     ` Steven Rostedt
2008-06-30 17:16   ` Gregory Haskins
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=4868B841.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