From: Peter Zijlstra <peterz@infradead.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why does the 2.6.37 scheduler hate RT tasks?
Date: Wed, 02 Feb 2011 12:14:25 +0100 [thread overview]
Message-ID: <1296645265.26581.307.camel@laptop> (raw)
In-Reply-To: <20110202011049.GA15084@linux.vnet.ibm.com>
On Tue, 2011-02-01 at 17:10 -0800, Paul E. McKenney wrote:
> Hello, Peter,
>
> If I create an SCHED_FIFO-priority kthread in pre-2.6.37 kernels,
> things work nicely. If I try in in later kernels, __disable_runtime()
> gets upset occasionally during CPU-hotplug calls when CPUs are inserted.
> If I make the exact same kthreads run SCHED_NORMAL, no problem.
> PS. The code at kernel/sched_rt.c:466 is "BUG_ON(want);" in
> __disable_runtime(). Config attached in case that helps.
Hrmm.. weird.. ok I'll have a look at that.
next prev parent reply other threads:[~2011-02-02 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 1:10 Why does the 2.6.37 scheduler hate RT tasks? Paul E. McKenney
2011-02-02 11:14 ` Peter Zijlstra [this message]
2011-02-14 14:55 ` Yong Zhang
2011-02-14 15:14 ` Paul E. McKenney
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=1296645265.26581.307.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.