Hi, i'm developing real-time application and i need to know relation between
RTAI
formatting link
2. RTLinux
formatting link
3. ingo molnar patch about kernel fully preemptive
formatting link
It is three patch to achieve the same goal ? or RTLinux/RTAI needs of (3) ? practical experience ?
thanks in advice.
Didn't find your answer? Ask the community — no account required.
I
Ignacio G. T.
El 22/11/2010 13:28, softwareEngineer escribió:
That's Linux on top of a specific real-time kernel.
Look for Xenomai too.
That's Linux on top of another specific real-time kernel, nowadays submerged in a windy river.
That's Linux with patches in its kernel.
No, those are two approaches (one: make Linux run as a task on top of an RTOS, use directly the RTOS when you need hard RT, but Linux apps when you don't; two: fix Linux kernel to make it more preemptable and less unpredictable, use always Linux applications) to solve the same problem. Each approach with its variations, trade marks and the like.
Not me... yet.
J
Juergen Beisert
RT preempt: The advantage is you can use generic POSIX (with exceptions) to program your hard realtime application and you can do it in userland. Successfully used in various industrial projects.
formatting link
jbe
S
sasho popov
(3) ?
If you need hard realtime you need to stick with RTL or RTAI. Both have a HAL beneath the linux jernel that provide hard-realtime API. If soft-RT is good enough for you the standard 2.6 kernel preforms pretty well as long as don't hit a s***ty driver ported from early 2.4 kernel versions. In 2.6 99% of the kernel code is preemtible (only the first level ISRs are not but those are well written in most cases)
I've used soft RT on 2.6 (and the latest 2.4) kernels without significant problems.
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required
Report Content
You are reporting this content to the moderators. They will look at it
ASAP.