From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Why does the 2.6.37 scheduler hate RT tasks?
Date: Mon, 14 Feb 2011 07:14:02 -0800 [thread overview]
Message-ID: <20110214151402.GA2256@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110214145549.GB2937@zhy>
On Mon, Feb 14, 2011 at 10:55:49PM +0800, Yong Zhang wrote:
> On Tue, Feb 01, 2011 at 05:10:49PM -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.
> >
> > Unfortunately, I need an RT kthread so that I can do priority boosting.
> >
> > My next thing to try is to demote my kthreads to SCHED_NORMAL at the
> > beginning of a CPU-hotplug event and promote them back to SCHED_FIFO at
> > the end of the CPU-hotplug event, which would leave the system vulnerable
> > to RCU priority inversion during CPU-hotplug events. This would be
> > better than the current behavior, but I thought that I should check with
> > you to see if there is a better approach.
>
> Just want to know the status of this issue :)
>
> Does commit 06c3bc655697b19521901f9254eb0bbb2c67e7e8 cure it?
Ah, good to see that this got in! I did extract it from the diagnostic
patch that Peter sent out, and it does seem to cure the issue.
Thanx, Paul
prev parent reply other threads:[~2011-02-14 15:14 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
2011-02-14 14:55 ` Yong Zhang
2011-02-14 15:14 ` Paul E. McKenney [this message]
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=20110214151402.GA2256@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=yong.zhang0@gmail.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