[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1002212322450.2811@localhost.localdomain>
Date: Mon, 22 Feb 2010 00:24:07 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: LKML <linux-kernel@...r.kernel.org>
cc: rt-users <linux-rt-users@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Carsten Emde <ce@...g.ch>,
Clark Williams <williams@...hat.com>,
Frank Rowand <frank.rowand@...sony.com>,
Robin Gareus <robin@...eus.org>,
Gregory Haskins <ghaskins@...ell.com>,
Philippe Reynes <philippe.reynes@...smpp.fr>,
Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>,
Will Schmidt <will_schmidt@...t.ibm.com>,
Darren Hart <dvhltc@...ibm.com>, Jan Blunck <jblunck@...e.de>,
Sven-Thorsten Dietrich <sdietrich@...ell.com>,
Jon Masters <jcm@...hat.com>,
Mark Knecht <markknecht@...il.com>,
John Kacur <jkacur@...hat.com>,
Nick Piggin <nickpiggin@...oo.com.au>
Subject: [ANNOUNCE] 2.6.33-rc8-rt1
We are pleased to announce the next update to our new preempt-rt
series.
- Forward to 2.6.33-rc8
Finally I managed to get that beast tamed.
Some folks were already joking, that my dog ate the 33-rt patch. The
truth is that my reject fixup skills were one line off in the mm/*
code which resulted in -rt eating my files :)
When I fixed the wreckage of my own stupidty I found out that -rt
triggered a nasty and hard to reproduce mainline scheduler bug, which
refused to reproduce with kernel tracing enabled. Thanks to Peter
Zijlstra for helping me to decode the initial mainline problem and the
ones which resulted from fixing the mainline bug!
It's all fixed now and I'm pretty happy about the state of this
release with the following exceptions:
1) it is only runtime tested on x86_64 (compiles on x86_32, arm,
powerpc_32/64).
I'm going to throw it at my testing infrastructure tomorrow, but I
wanted to release this before .33-final and of course you folks
are heartely invited to help out with fixing the fallout :)
2) I broke the histogram tracer stuff simply because I got lost in
the divergence of -rt and mainline kernel/trace/* changes
I apologize to Carsten, but I'm sure he will fix that in no time
as usual
The current state of the patch on x86_64 is: rock stable!
[rt-tests]# chrt -f 1 ./cyclictest -t -a -n -d0 -p80 -i125
policy: fifo: loadavg: 509.19 490.53 486.66 364/1055 31899
T: 0 (27682) P:80 I:125 C:1170997397 Min: 2 Act: 3 Avg: 3 Max: 34
T: 1 (27683) P:79 I:125 C:1170997397 Min: 2 Act: 3 Avg: 3 Max: 34
That's an uptime of ~1.6 days with a load of hackbench, recursive
grep and extensive networking traffic going on.
The merge of the spinlock namespace cleanup and the initial
annotations took a big chunk away from the -rt patch size:
patch-2.6.31.12-rt21.patch 1680354
patch-2.6.33-rc8.patch 1179390
patch-2.6.33-rc8+git.patch 1067064
We are zooming in, but there is still a way to go!
Download locations:
http://rt.et.redhat.com/download/ (temporary out of sync)
http://www.kernel.org/pub/linux/kernel/projects/rt/
Git development branch:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head
Git release branch:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33
Gitweb:
http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33
Information on the RT patch can be found at:
http://rt.wiki.kernel.org/index.php/Main_Page
To build the 2.6.33-rc8-rt1 tree, the following patches should be
applied:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.tar.bz2
http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.33-rc8.bz2
http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rc8-rt1.bz2
Enjoy !
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists