Q17Real Time Systems

A General Purpose Operating System (GPOS like Windows or standard Linux) and a Real-Time Operating System (RTOS like VxWorks) are architecturally fundamentally opposed. A GPOS is designed for human comfort and massive throughput; an RTOS is designed strictly for machine-level mathematical physics.

• 1. Determinism vs. Fairness: A GPOS uses mathematical "Fairness" algorithms. If a low-priority background task is starving, a GPOS will eventually temporarily boost its priority to let it run. An RTOS is a violent dictator. It NEVER boosts priority for fairness. If a low-priority task starves to death because a high-priority task needs the CPU 100% of the time, the RTOS mathematically executes that starvation without hesitation.
• 2. Interrupt Latency: When a hardware interrupt fires, a GPOS might block it for several milliseconds to finish a critical kernel disk write. An RTOS guarantees that interrupts are mathematically unmasked and handled in extremely bounded, microscopic timeframes (e.g., $<10$ microseconds).
• 3. Preemption: A GPOS kernel is often non-preemptible (or only partially preemptible). If the OS is executing a system call, it cannot be interrupted. An RTOS kernel is violently fully preemptible. A high-priority task can rip the CPU away from the OS itself at almost any exact instruction cycle.
• 4. Virtual Memory (Paging): A GPOS aggressively uses the hard drive as fake RAM (Pagefile/Swap). If memory is accessed, it triggers a Page Fault, causing a massive, chaotic disk read latency. An RTOS mathematically bans page faults. All critical task memory is violently locked into physical silicon RAM to guarantee absolute, predictable execution times.