From: Dragan Noveski <perodog@gmx.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: 2.6.23.1-rt9 (and others)
Date: Wed, 07 Nov 2007 14:17:50 +0000 [thread overview]
Message-ID: <4731C90E.7030509@gmx.net> (raw)
In-Reply-To: <1194413959.8827.66.camel@localhost.localdomain>
Steven Rostedt wrote:
> This is a special announcement for the latest -rt patches. This is
> actually announcing more than one tree (pay close attention to the
> differences between -rt7, -rt8 and -rt9).
>
> 2.6.23.1-rt6
>
> - Removed BUG_ON in exit (Steven Rostedt and Daniel Walker)
>
> - Turn RCU preempt boost on by default (Steven Rostedt)
> (for when RCU PREEMPT is enabled)
>
> - Fixes for PowerPC (Paul McKenney)
>
>
> 2.6.23.1-rt7
>
> - Found that there's a flaw in the PowerPC patch so
> it was pulled from the tree.
>
> 2.6.23.1-rt8
>
> - More aggressive RT Balancing (Gregory Haskins)
>
> 2.6.23.1-rt9
>
> - RT balancing by CPU priorities (Gregory Haskins)
>
>
> Now benchmarks against 2.6.23.1-rt7 -rt8 and -rt9 would be greatly
> appreciated. These three are all present in
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/
>
> Gregory and I have been having disagreements on how to solve RT task
> balancing among CPUS. Although we shared ideas back and forth, and both
> our methods have been greatly influenced by each other, the real answer
> comes from actual numbers. So these three versions are posted for your
> convenience to see which actually do the best. I would be happy to tell
> Gregory he's right, if the numbers prove it.
>
> Currently, what we do to test RT latencies is to run Thomas Gleixner's
> cyclictest
> (http://git.kernel.org/?p=linux/kernel/git/tglx/rt-tests.git;a=summary)
> as well as hackbench, to see what the maximum latencies we get are.
>
> Other tests are welcomed too.
>
>
> to build a 2.6.23.1-rt7 tree, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.1.tar.bz2
> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.23.1-rt7.bz2
>
> to build a 2.6.23.1-rt8 tree, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.1.tar.bz2
> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.23.1-rt8.bz2
>
> to build a 2.6.23.1-rt9 tree, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.1.tar.bz2
> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.23.1-rt9.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-rt1
>
> The broken out patches are also available.
>
> Thanks!
>
> -- Steve
>
>
hallo, i just tried to compile rt9 and rt7 and both times i get this
error at about the end of the 'make && make modules' step:
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
kernel/built-in.o: In function `sched_init':
(.init.text+0x1af): undefined reference to `cpupri_init'
make: *** [.tmp_vmlinux1] Fehler 1
i am on uniprozessor machine here, IBM-thinkpad-r50e + debian testing.
if you need parts of my config file, just feel free to tell me so and i
ll try to provide you the information!
cheers,
doc
next prev parent reply other threads:[~2007-11-07 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 5:39 2.6.23.1-rt9 (and others) Steven Rostedt
2007-11-07 14:17 ` Dragan Noveski [this message]
2007-11-07 13:40 ` Gregory Haskins
2007-11-07 15:10 ` Dragan Noveski
2007-11-07 16:33 ` Steven Rostedt
2007-11-07 20:40 ` Dragan Noveski
2007-11-07 18:10 ` Dragan Noveski
2007-11-07 18:11 ` Dragan Noveski
2007-11-07 14:20 ` [PATCH] RT: fix uniprocessor build issue with new scheduler enhancements Gregory Haskins
2007-11-07 15:41 ` 2.6.23.1-rt9 (and others) Steven Rostedt
2007-11-07 22:51 ` Gregory Haskins
2007-11-07 20:41 ` Dragan Noveski
2007-11-07 19:59 ` Steven Rostedt
2007-11-07 21:04 ` Dragan Noveski
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=4731C90E.7030509@gmx.net \
--to=perodog@gmx.net \
--cc=linux-rt-users@vger.kernel.org \
/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.