* Updated realtime-preempt documentation
@ 2005-04-30 5:37 mjc
2005-04-30 6:11 ` Lee Revell
` (3 more replies)
0 siblings, 4 replies; 7+ messages in thread
From: mjc @ 2005-04-30 5:37 UTC (permalink / raw)
To: linux-kernel
Hey all,
I've been following Ingo Molnar and friends' lovely realtime-preempt
patchset. I'm curious, though, the only piece of documentation I've
found is
http://people.redhat.com/mingo/realtime-preempt/older/ANNOUNCE-voluntary-preempt
which is, indeed, quite old. Is anyone planning on updating this in
the near future or is it in too much flux? Should I try and make heads or
tails of the code first?
-
Michael
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Updated realtime-preempt documentation
2005-04-30 5:37 Updated realtime-preempt documentation mjc
@ 2005-04-30 6:11 ` Lee Revell
2005-04-30 14:28 ` Daniel Walker
2005-04-30 14:22 ` Daniel Walker
` (2 subsequent siblings)
3 siblings, 1 reply; 7+ messages in thread
From: Lee Revell @ 2005-04-30 6:11 UTC (permalink / raw)
To: mjc; +Cc: linux-kernel
On Sat, 2005-04-30 at 01:37 -0400, mjc@unre.st wrote:
> Hey all,
>
> I've been following Ingo Molnar and friends' lovely realtime-preempt
> patchset. I'm curious, though, the only piece of documentation I've
> found is
> http://people.redhat.com/mingo/realtime-preempt/older/ANNOUNCE-voluntary-preempt
> which is, indeed, quite old. Is anyone planning on updating this in
> the near future or is it in too much flux? Should I try and make heads or
> tails of the code first?
I think it's changing too fast for anyone to have bothered to document
it yet.
But, you could make some pretty good documentation based on the LKML
discussions of RT preemption, especially Ingo's posts.
Lee
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Updated realtime-preempt documentation
2005-04-30 6:11 ` Lee Revell
@ 2005-04-30 14:28 ` Daniel Walker
2005-04-30 18:17 ` Lee Revell
0 siblings, 1 reply; 7+ messages in thread
From: Daniel Walker @ 2005-04-30 14:28 UTC (permalink / raw)
To: Lee Revell; +Cc: mjc, linux-kernel
On Sat, 30 Apr 2005, Lee Revell wrote:
>
> I think it's changing too fast for anyone to have bothered to document
> it yet.
That's true for some of it, but like interrupts in threads hasn't changed
in a few months .. The config options aren't likely to change ..
> But, you could make some pretty good documentation based on the LKML
> discussions of RT preemption, especially Ingo's posts.
That would be a chore ..
Daniel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Updated realtime-preempt documentation
2005-04-30 5:37 Updated realtime-preempt documentation mjc
2005-04-30 6:11 ` Lee Revell
@ 2005-04-30 14:22 ` Daniel Walker
2005-04-30 15:39 ` john cooper
2005-04-30 20:31 ` Jonathan Corbet
3 siblings, 0 replies; 7+ messages in thread
From: Daniel Walker @ 2005-04-30 14:22 UTC (permalink / raw)
To: mjc; +Cc: linux-kernel
On Sat, 30 Apr 2005 mjc@unre.st wrote:
> Hey all,
>
> I've been following Ingo Molnar and friends' lovely realtime-preempt
> patchset. I'm curious, though, the only piece of documentation I've
> found is
> http://people.redhat.com/mingo/realtime-preempt/older/ANNOUNCE-voluntary-preempt
> which is, indeed, quite old. Is anyone planning on updating this in
> the near future or is it in too much flux? Should I try and make heads or
> tails of the code first?
No free documentation exists that I know of. It would be nice if someone
wrote some..
What would you like to know?
Daniel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Updated realtime-preempt documentation
2005-04-30 5:37 Updated realtime-preempt documentation mjc
2005-04-30 6:11 ` Lee Revell
2005-04-30 14:22 ` Daniel Walker
@ 2005-04-30 15:39 ` john cooper
2005-04-30 20:31 ` Jonathan Corbet
3 siblings, 0 replies; 7+ messages in thread
From: john cooper @ 2005-04-30 15:39 UTC (permalink / raw)
To: mjc; +Cc: linux-kernel, john cooper
mjc@unre.st wrote:
> Hey all,
>
> I've been following Ingo Molnar and friends' lovely realtime-preempt
> patchset. I'm curious, though, the only piece of documentation I've
> found is
> http://people.redhat.com/mingo/realtime-preempt/older/ANNOUNCE-voluntary-preempt
> which is, indeed, quite old. Is anyone planning on updating this in
> the near future or is it in too much flux? Should I try and make heads or
> tails of the code first?
I'd cobbled together documentation for internal use here
though it lacks an "overall concepts" wrapper. I should
be revisiting this in a week or so and will look into
making it generally available.
-john
--
john.cooper@timesys.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Updated realtime-preempt documentation
2005-04-30 5:37 Updated realtime-preempt documentation mjc
` (2 preceding siblings ...)
2005-04-30 15:39 ` john cooper
@ 2005-04-30 20:31 ` Jonathan Corbet
3 siblings, 0 replies; 7+ messages in thread
From: Jonathan Corbet @ 2005-04-30 20:31 UTC (permalink / raw)
To: mjc; +Cc: linux-kernel
> I've been following Ingo Molnar and friends' lovely realtime-preempt
> patchset. I'm curious, though, the only piece of documentation I've
> found is
> http://people.redhat.com/mingo/realtime-preempt/older/ANNOUNCE-voluntary-preempt
> which is, indeed, quite old. Is anyone planning on updating this in
> the near future or is it in too much flux?
Don't know if it's what you're after, but I've written some on the
realtime preemption patches:
http://lwn.net/Articles/106010/
http://lwn.net/Articles/107269/
http://lwn.net/Articles/108216/
http://lwn.net/Articles/129511/
jon
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2005-04-30 20:34 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-30 5:37 Updated realtime-preempt documentation mjc
2005-04-30 6:11 ` Lee Revell
2005-04-30 14:28 ` Daniel Walker
2005-04-30 18:17 ` Lee Revell
2005-04-30 14:22 ` Daniel Walker
2005-04-30 15:39 ` john cooper
2005-04-30 20:31 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox