| Delivered production code
|
Work in progress.
|
| Current worst case timing is in the low microseconds when you torture the controlling machine.
|
Current worst case timing is multiple milliseconds when you baby the controlling machine, much worse if you make it do something productive.
|
| Clear technology path to further optimizations.
|
Goal of 2 or 3 times performance degradation over current RTLinux.
|
| X86 (486 and up), PowerPC (most versions), StrongArm, MIPS, Alpha
|
Pentium III and up.
|
| SMP.
|
Not yet.
|
| Great low memory performance.
|
All tests on big memory systems.
|
| RT code uses stable FSMLabs POSIX threads API.
|
Guaranteed non-stable kernel driver environment.
|
| No Linux kernel expertise needed.
|
Write your own Linux kernel drivers.
|
| Recompile Linux drivers to make them RT safe.
|
Audit, by hand, all Linux drivers for timing.
|
| POSIX threads, scheduling, signals, mutexes, semaphores for RT code.
|
Anything you need in Linux drivers, you write.
|
| Non-blocking interfaces between RT and non-RT, designed to avoid priority inversion.
|
Good luck.
|
| RT code ports to multiple Linux versions and to BSD.
|
RT code will be specific to “custom drivers” and special versions of Linux that have preemption.
|
| Modular programming environment.
|
Monolithic programming environment, subject to unpredicatable shifts.
|