From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: [ANNOUNCE] 3.12.14-rt23
Date: Fri, 21 Mar 2014 21:13:53 +0100 [thread overview]
Message-ID: <20140321201353.GB28289@linutronix.de> (raw)
Dear RT folks!
I'm pleased to announce the v3.12.14-rt23 patch set.
Changes since v3.12.14-rt22
- Helmut Buchsbaum run into OOM because RCU did not have enough time to
free memory. The problem appeared while the RCU softirq has been
replaced by the RCU thread. The problem can be "fixed" by giving a
higher priority to the RCU thread or by just enabled the "RCU_BOOST"
kernel option. The kernel option is now enabled by default on an -RT
enabled system and can be disabled by the user if desired.
Known issues:
- bcache is disabled.
The delta patch against v3.12.14-rt22 is appended below and can be found
here:
https://www.kernel.org/pub/linux/kernel/projects/rt/3.12/incr/patch-3.12.14-rt22-rt23.patch.xz
The RT patch against 3.12.14 can be found here:
https://www.kernel.org/pub/linux/kernel/projects/rt/3.12/patch-3.12.14-rt23.patch.xz
The split quilt queue is available at:
https://www.kernel.org/pub/linux/kernel/projects/rt/3.12/patches-3.12.14-rt23.tar.xz
Sebastian
diff --git a/init/Kconfig b/init/Kconfig
index 4dea595..f6aeea6 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -642,7 +642,7 @@ config TREE_RCU_TRACE
config RCU_BOOST
bool "Enable RCU priority boosting"
depends on RT_MUTEXES && PREEMPT_RCU
- default n
+ default y if PREEMPT_RT_FULL
help
This option boosts the priority of preempted RCU readers that
block the current preemptible RCU grace period for too long.
diff --git a/localversion-rt b/localversion-rt
index c29508d..9a218ca 100644
--- a/localversion-rt
+++ b/localversion-rt
@@ -1 +1 @@
--rt22
+-rt23
reply other threads:[~2014-03-21 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140321201353.GB28289@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).