From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
dipankar@in.ibm.com, tytso@us.ibm.com, dvhltc@us.ibm.com,
oleg@tv-sign.ru, twoerner.k@gmail.com, josh@freedesktop.org,
billh@gnuppy.monkey.org, nielsen.esben@googlemail.com,
corbet@lwn.net
Subject: Re: [RFC PATCH -rt 1/2] RCU priority boosting that survives vicious testing
Date: Thu, 1 Feb 2007 09:23:33 +0100 [thread overview]
Message-ID: <20070201082333.GA18233@elte.hu> (raw)
In-Reply-To: <20070201012445.GA22922@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Here is the RCU priority-boosting patch. Pretty close to the
> http://lkml.org/lkml/2007/1/24/295 version. This patch prevents
> preempted or blocked low-priority RCU readers from indefinitely
> stalling RCU grace periods.
thanks - i've applied both patches to -rt and it's looking good so far!
Find a small cosmetic fix below.
Ingo
Index: linux/kernel/rcupreempt.c
===================================================================
--- linux.orig/kernel/rcupreempt.c
+++ linux/kernel/rcupreempt.c
@@ -489,7 +489,7 @@ void init_rcu_boost_late(void)
rcu_boost_task = kthread_run(rcu_booster, NULL, "RCU Prio Booster");
if (IS_ERR(rcu_boost_task)) {
printk(KERN_ALERT
- "Unable to create RCU Priority Booster, errno %d\n",
+ "Unable to create RCU Priority Booster, errno %ld\n",
-PTR_ERR(rcu_boost_task));
/*
next prev parent reply other threads:[~2007-02-01 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 1:21 [RFC PATCH -rt 0/2] RCU priority boosting that survives vicious testing Paul E. McKenney
2007-02-01 1:24 ` [RFC PATCH -rt 1/2] " Paul E. McKenney
2007-02-01 8:23 ` Ingo Molnar [this message]
2007-02-02 15:56 ` Paul E. McKenney
2007-02-01 1:26 ` [RFC PATCH -rt 2/2] RCU priority boosting additions to rcutorture Paul E. McKenney
2007-02-01 2:12 ` Nigel Cunningham
2007-02-01 2:31 ` Paul E. McKenney
2007-02-01 2:42 ` Nigel Cunningham
2007-02-01 5:46 ` Paul E. McKenney
2007-02-01 22:13 ` Nigel Cunningham
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=20070201082333.GA18233@elte.hu \
--to=mingo@elte.hu \
--cc=billh@gnuppy.monkey.org \
--cc=corbet@lwn.net \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nielsen.esben@googlemail.com \
--cc=oleg@tv-sign.ru \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=twoerner.k@gmail.com \
--cc=tytso@us.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.