You could look at http://www.rtlinux.com or at http://www.fsmlabs.com. EL/IX does not currently feature as part of our API roadmap. Tip: In the Linux world, one way to find out about Linux projects is to look in the MAINTAINERS file in the Linux source.
I think the microkernel versus monolithic kernel technical argument has been long since lost by the microkernel people. RTLinux offers no memory protection for RT tasks because the RTLinux design calls for putting only the absolute necessary RT components on the RT side and making those as absolutely low overhead as possible. QNX has a different model, and QNX is a very good system, but they have a harder time providing good worst case timings. For machine control, worst case, not typical case, is the number that is interesting.
The api for RTLinux is still evolving and I want to make sure that current RTLinux users don't get too worried about the resolutions of a group of users of RTLinux and other flavors of "real time" on Linux. For us, backwards compatibility and performance are essential and I am not yet convinced that the Cygnus API is such an advance. RTLinux, however, supports the main API as part of a scheduler module and I look forward to seeing proof of concept in an EL/IX module.
Slashdot Mirror
RTLinux switches tasks in microseconds - and not many microseconds.
You could look at http://www.rtlinux.com or at http://www.fsmlabs.com. EL/IX does not currently feature as part of our API roadmap. Tip: In the Linux world, one way to find out about Linux projects is to look in the MAINTAINERS file in the Linux source.
I think the microkernel versus monolithic kernel technical argument has been long since lost by the microkernel people. RTLinux offers no memory protection for RT tasks because the RTLinux design calls for putting only the absolute necessary RT components on the RT side and making those as absolutely low overhead as possible. QNX has a different model, and QNX is a very good system, but they have a harder time providing good worst case timings. For machine control, worst case, not typical case, is the number that is interesting.
The api for RTLinux is still evolving and I want to make sure that current RTLinux users don't get too worried about the resolutions of a group of users of RTLinux and other flavors of "real time" on Linux. For us, backwards compatibility and performance are essential and I am not yet convinced that the Cygnus API is such an advance. RTLinux, however, supports the main API as part of a scheduler module and I look forward to seeing proof of concept in an EL/IX module.