Is Linux a Real‑Time or Time‑Sharing OS? Understanding RTOS vs TSOS

1. Real‑Time Operating System (RTOS)

RTOS (Real Time Operating System) is an operating system that can receive external events or data and process them quickly enough so that the results are produced within a specified deadline, ensuring timely control of production processes.

It is divided into hard real‑time, which must meet the deadline under any circumstance, and soft real‑time, which strives to finish as fast as possible according to task priority.

Key features include multitasking, thread priority, multiple interrupt levels, and the ability to guarantee deterministic response.

Relevant concepts :

Critical section – code that cannot be interrupted once started.

Resources – any entity occupied by a task.

Shared resources – can be used by more than one task.

Task – a thread with its own priority, registers, and stack, typically cycling through states such as sleeping, ready, running, suspended, and interrupted.

Task switching – saving the current task’s CPU context and restoring the next task’s context.

Kernel – manages tasks, allocates CPU time, and handles inter‑task communication; can be pre‑emptive or non‑pre‑emptive.

Scheduling – usually priority‑based.

Priority types – static (unchangeable) and dynamic (adjustable).

Priority inversion – a low‑priority task holds a shared resource needed by a high‑priority task; solved by priority inheritance.

Mutual exclusion – achieved by disabling interrupts, test‑and‑set instructions, disabling task switches, or using semaphores.

Interrupt response time is a primary performance metric for embedded RTOS and is defined as:

Interrupt response time = Interrupt latency + Time to save CPU state + ISR execution time

Interrupt latency = MAX(longest interrupt‑disable time, longest instruction time) + time of the first ISR instruction.

2. Time‑Sharing Operating System (TSOS)

TSOS (Time‑Sharing Operating System) is an OS that allows a computer to serve multiple users simultaneously by dividing CPU time into short time slices and rotating them among user processes.

It enables interactive, multi‑user environments where each user perceives exclusive use of the machine.

Basic idea : the system’s resources, especially CPU time, are partitioned into time slices; each user’s program runs for one slice before the scheduler switches to the next.

Typical examples include UNIX, which uses pre‑emptive, dynamic‑priority scheduling to support time‑sharing.

Design goals are timely response to user requests and maximizing resource utilization.

Characteristics :

Interactivity – human‑machine dialogue.

Multiplexing – many users share a single CPU.

Independence – users operate without interfering with each other.

Timeliness – users receive prompt answers.

Factors affecting response time: number of terminals, time‑slice length, amount and speed of data exchange.

3. Comparison

RTOS is typically used on low‑speed microcontrollers (MCUs) where millisecond or microsecond response is required, such as motion control or button input handling.

TSOS is used on PCs and servers, where the CPU is divided into many time slices to serve dozens or hundreds of users.

Thus, Linux is fundamentally a time‑sharing operating system, but it can be transformed into a real‑time system by applying real‑time patches (e.g., PREEMPT‑RT, resulting in variants like uClinux).

Original source: https://www.cnblogs.com/xiawen/p/3317302.html