From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>, RT <linux-rt-users@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: 2.6.24.7-rt8
Date: Tue, 20 May 2008 00:46:03 -0400 [thread overview]
Message-ID: <1211258763.14697.82.camel@localhost.localdomain> (raw)
We are pleased to announce the 2.6.24.7-rt8 tree, which can be
downloaded from the location:
http://rt.et.redhat.com/download/
Information on the RT patch can be found at:
http://rt.wiki.kernel.org/index.php/Main_Page
Changes since 2.6.24.7-rt7
- Read Write locks with multiple readers (Steven Rostedt)
The previous versions of the RT tree would serialize the RW locks
for all readers to allow for priority inheritance to take place.
This change allows for multiple readers but still maintain priority
inheritance. The number of readers that can hold a lock at any time
may be limited by
sysctl kernel.rwlocks_reader_limit
Setting this to <= 0 will give allow for any number of readers. The
default is set to NR_CPUS.
** Note: I made this change separate to allow for easy testing in case
bugs have been introduced by this change.
to build a 2.6.24.7-rt8 tree, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.24.tar.bz2
http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.24.7.bz2
http://rt.et.redhat.com/download/patch-2.6.24.7-rt8.bz2
And like always, my RT version of Matt Mackall's ketchup will get this
for you nicely:
http://people.redhat.com/srostedt/rt/tools/ketchup-0.9.8-rt3
The broken out patches are also available.
-- Steve
next reply other threads:[~2008-05-20 4:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 4:46 Steven Rostedt [this message]
2008-05-21 6:25 ` 2.6.24.7-rt8 Mike Galbraith
2008-05-21 6:27 ` 2.6.24.7-rt8 Mike Galbraith
2008-05-21 12:47 ` 2.6.24.7-rt8 Steven Rostedt
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=1211258763.14697.82.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®