From: Ryan Brown <some.nzguy@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
george anzinger <george@mvista.com>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.53-01, High Resolution Timers & RCU-tasklist features
Date: Sat, 13 Aug 2005 12:28:43 +1200 [thread overview]
Message-ID: <1c1c8636050812172817b14384@mail.gmail.com> (raw)
In-Reply-To: <20050811110051.GA20872@elte.hu>
is there a patch available for -rc6?
On 8/11/05, Ingo Molnar <mingo@elte.hu> wrote:
>
> i have released the -53-01 Real-Time Preemption patch, which can be
> downloaded from:
>
> http://redhat.com/~mingo/realtime-preempt/
>
> there are two new features in this release, which justified the jump
> from .52 to .53:
>
> - the inclusion of the High Resolution Timers patch, written by
> George Anzinger, and ported/improved/cleaned-up by Thomas Gleixner.
>
> - the inclusion of the RCU tasklist_lock patch from Paul McKenney.
>
> the HRT patch from George Anzinger is a crutial piece of real-time
> infrastructure. The version included in the -RT tree supports both PIT
> and local APIC timer driven variable-rate timer interrupts.
>
> Thomas Glexiner, besides porting it to PREEMPT_RT, cleaning it up,
> adding the local APIC timer support has also added the
> CONFIG_HIGH_RES_TIMERS_DYN_PRIO feature, which pushes priority
> inheritance into the high-res timer space. Furthermore, Thomas has
> extended nanosleep to use HR timers, if the task is RT. This makes it
> easier to test HRT functionality.
>
> NOTE: there's a new softirq, softirq-hrtimer (PID 8 on UP x86), which
> should be chrt-ed to higher than SCHED_FIFO-50 if HR timer interrupts
> are the most important latencies in the system. E.g.:
>
> chrt -f 90 -p 8
>
> the RCU tasklist-lock patch is a small but important feature from Paul
> McKenney which enables good HRT latencies: the HRT patch, when using
> POSIX timers, would use a signal-sending codepath that depends on the
> tasklist_lock, and thus the (quite high) tasklist_lock latencies
> controlled the latency of HR timers - defeating much of the benefits of
> HR timers. With the RCU tasklist-lock the signal sending path is now
> RCU-read locked, with no locking dependency, and thus excellent
> worst-case latencies.
>
> given these changes, some (mostly build-related) regressions are to be
> expected. Only the x86 architecture is expected to work for now.
>
> to build a -V0.7.53-01 tree, the following patches should to be applied:
>
> http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.12.tar.bz2
> http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.13-rc4.bz2
> http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.13-rc4-RT-V0.7.53-01
>
> patches, bugreports and any other feedback welcome,
>
> Ingo
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-08-13 0:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 11:00 [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.53-01, High Resolution Timers & RCU-tasklist features Ingo Molnar
2005-08-12 3:07 ` Lee Revell
2005-08-12 3:19 ` Lee Revell
2005-08-12 7:03 ` Ingo Molnar
2005-08-12 7:48 ` Thomas Gleixner
2005-08-12 7:07 ` Ingo Molnar
2005-08-13 0:28 ` Ryan Brown [this message]
2005-08-13 0:32 ` Lee Revell
2005-08-13 0:57 ` George Anzinger
2005-08-14 2:12 ` Ingo Molnar
2005-08-15 6:29 ` Ingo Molnar
2005-08-15 23:39 ` George Anzinger
2005-08-16 6:36 ` Thomas Gleixner
2005-08-15 11:18 ` [patch] Real-Time Preemption, -RT-2.6.13-rc6-V0.7.53-11 Ingo Molnar
2005-08-15 20:35 ` Peter Zijlstra
2005-08-16 3:53 ` Ingo Molnar
2005-08-16 14:35 ` Alan Stern
2005-08-16 16:12 ` Ingo Molnar
2005-08-16 16:56 ` Alan Stern
2005-08-16 17:02 ` Ingo Molnar
2005-08-17 2:23 ` David Brownell
2005-08-17 14:10 ` Alan Stern
2005-08-17 20:51 ` David Brownell
2005-08-18 4:52 ` Ingo Molnar
2005-08-18 6:37 ` David Brownell
2005-08-18 14:43 ` Alan Stern
2005-08-22 11:07 ` Ingo Molnar
2005-08-17 6:31 ` Ingo Molnar
2005-08-16 8:41 ` 2.6.13-rc6-rt1 Ingo Molnar
2005-08-16 12:32 ` 2.6.13-rc6-rt1 Michal Schmidt
2005-08-27 1:15 ` 2.6.13-rc6-rt1 Matt Mackall
2005-08-29 22:36 ` 2.6.13-rc6-rt1 Esben Nielsen
2005-08-17 0:53 ` [patch] KGDB for Real-Time Preemption systems George Anzinger
2005-08-17 6:53 ` Ingo Molnar
2005-08-17 19:16 ` George Anzinger
2005-09-05 12:23 ` Serge Noiraud
2005-09-08 0:37 ` George Anzinger
2005-09-07 8:55 ` Serge Noiraud
2005-09-07 21:16 ` George Anzinger
2005-09-08 8:57 ` Serge Noiraud
2005-09-08 20:47 ` George Anzinger
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 18:39 [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.53-01, High Resolution Timers & RCU-tasklist features Guillaume Foliard
2005-08-12 12:53 ` Ingo Molnar
2005-08-12 19:27 ` Guillaume Foliard
2005-08-12 19:47 ` Guillaume Foliard
2005-08-12 20:07 ` Chuck Harding
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=1c1c8636050812172817b14384@mail.gmail.com \
--to=some.nzguy@gmail.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--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