OS Architecture
What is OS Architecture?
OS Architecture refers to the internal design and organization of an operating system—how its components are arranged and how they communicate with each other.
An OS contains many components:
- Process management
- Memory management
- File system
- I/O management
- Device management
- Networking
- Security
- System-call interface
- Kernel
OS architecture determines where these components run and how they interact.
Basic OS Architecture
A simplified operating system can be represented as:
+----------------------------------+ | USERS | +----------------------------------+ ↓ +----------------------------------+ | APPLICATION PROGRAMS | | Chrome | VS Code | VLC | Games | +----------------------------------+ ↓ +----------------------------------+ | SYSTEM CALL INTERFACE | +----------------------------------+ ↓ +----------------------------------+ | KERNEL | | | | Process Management | | Memory Management | | File System | | I/O Management | | Device Management | | Network Management | | Security | +----------------------------------+ ↓ +----------------------------------+ | HARDWARE | | CPU | RAM | Disk | Devices | +----------------------------------+
The kernel is the central part of most operating-system architectures.
Main Components of OS Architecture
1. User Interface
The user interface allows users to interact with the system.
Two major interfaces are:
GUI
Graphical User Interface.
Examples:
Windows Desktop Linux GNOME macOS Finder
Users interact using:
- Windows
- Icons
- Menus
- Buttons
- Mouse
- Touch
CLI
Command Line Interface.
Example:
ls cd Documents mkdir project
2. System Call Interface
Applications normally cannot directly access protected hardware resources.
Instead, they request services from the OS through system calls.
Example:
Application ↓ System Call ↓ Kernel ↓ Hardware
For example, when a program wants to read a file:
Program ↓ read() ↓ Kernel ↓ File System ↓ Storage Device
System calls will be covered in detail in your next topic.
3. Kernel
The kernel is the core component of the operating system.
It manages privileged operations and important system resources.
Major kernel responsibilities include:
Process Management
Managing processes and CPU scheduling.
Process A Process B Process C ↓ Kernel ↓ CPU
Memory Management
Managing RAM and virtual memory.
Applications ↓ Memory Manager ↓ RAM
File Management
Managing files and directories.
Application ↓ File System ↓ Storage
Device Management
Managing hardware devices through device drivers.
Application ↓ Kernel ↓ Driver ↓ Device
Types of OS Architecture
The major architectures you should know are:
- Simple/Monolithic Architecture
- Layered Architecture
- Microkernel Architecture
- Modular Architecture
- Hybrid Architecture
- Exokernel Architecture
1. Simple / Monolithic Architecture
In a monolithic architecture, many operating-system services run inside one large kernel.
Simplified:
+--------------------------+ | Applications | +--------------------------+ ↓ +--------------------------+ | System Calls | +--------------------------+ ↓ +--------------------------+ | MONOLITHIC KERNEL | | | | Process Management | | Memory Management | | File System | | Device Drivers | | Networking | | I/O Management | +--------------------------+ ↓ +--------------------------+ | Hardware | +--------------------------+
Most core OS functionality operates in kernel space.
Advantages
- High performance
- Direct communication between components
- Relatively fast system calls
Disadvantages
- Large kernel
- A bug in one kernel component can potentially affect the entire system
- More difficult to maintain as the kernel becomes large
Example
Traditional Unix systems are often described as monolithic.
Modern Linux is also generally classified as a monolithic kernel, although it has a modular design that allows many components to be loaded dynamically.
2. Layered Architecture
In a layered OS architecture, the operating system is divided into different layers.
Each layer provides services to the layer above it.
Example:
+---------------------------+ | Layer 5: User Programs | +---------------------------+ | Layer 4: User Interface | +---------------------------+ | Layer 3: File System | +---------------------------+ | Layer 2: Memory/Process | +---------------------------+ | Layer 1: Device Drivers | +---------------------------+ | Layer 0: Hardware | +---------------------------+
The exact number and organization of layers vary by system.
Principle
Higher Layer ↓ Uses services of ↓ Lower Layer
For example:
Application ↓ File System ↓ Device Driver ↓ Hardware
Advantages
- Easier to design
- Easier to understand
- Easier to debug
- Clear separation of responsibilities
Disadvantages
- Defining perfect layers can be difficult
- Additional layers can introduce overhead
- Some functions naturally need to interact across layers
3. Microkernel Architecture
A microkernel keeps only the most essential functions inside the kernel.
Other services run outside the kernel, often as separate processes in user space.
The microkernel typically provides mechanisms such as:
- Basic process/thread management
- Inter-process communication (IPC)
- Basic memory/address-space management
- Low-level scheduling
Other services may run outside the kernel.
+--------------------------------+ | Applications | +--------------------------------+ ↓ +--------------------------------+ | User-Space Services | | | | File Server | | Network Server | | Device Services | | Other OS Services | +--------------------------------+ ↓ +--------------------------------+ | MICROKERNEL | | | | IPC | | Basic Scheduling | | Basic Memory Management | +--------------------------------+ ↓ +--------------------------------+ | Hardware | +--------------------------------+
Main Idea
Keep the kernel as small as possible.
Advantages
- Smaller trusted kernel
- Better fault isolation
- Easier to maintain and extend
- Potentially better security
If a user-space service crashes, it may be possible to restart that service without crashing the entire OS.
Disadvantages
- Communication between components can introduce overhead
- More complex system design
- Performance can be affected if too much work requires IPC
Examples
Microkernel-based systems include QNX and MINIX 3.
4. Modular Architecture
A modular kernel has a core kernel plus modules that can be loaded or unloaded when needed.
Example:
+-----------------------------+ | Applications | +-----------------------------+ ↓ +-----------------------------+ | Kernel Core | +-----------------------------+ ↓ ↓ ↓ Module Module Module Driver Network FileSystem +-----------------------------+ | Hardware | +-----------------------------+
For example, a Linux system can load kernel modules for particular hardware or functionality.
Advantages
- Flexible
- Easier to extend
- Modules can often be loaded without rebuilding the entire kernel
- Good balance between performance and modularity
Disadvantages
- Kernel modules still execute with high privileges
- A faulty module can potentially cause serious system problems
5. Hybrid Architecture
A hybrid architecture combines ideas from multiple architectural approaches, especially monolithic and microkernel designs.
Simplified:
+---------------------------+ | Applications | +---------------------------+ ↓ +---------------------------+ | System Services | +---------------------------+ ↓ +---------------------------+ | Hybrid Kernel | | | | Core Services | | Drivers | | Memory Management | | Process Management | | File System | +---------------------------+ ↓ +---------------------------+ | Hardware | +---------------------------+
The goal is generally to combine:
- Performance
- Modularity
- Flexibility
- Fault isolation where practical
Examples commonly described as using hybrid-kernel designs include Windows NT-family kernels and Apple's XNU.
6. Exokernel Architecture
An Exokernel takes a different approach.
Instead of providing a large set of high-level abstractions inside the kernel, it tries to provide applications with secure and controlled access to hardware resources.
Simplified:
+----------------------------+ | Applications / Libraries | +----------------------------+ ↓ +----------------------------+ | Exokernel | | Resource Protection | | Resource Allocation | +----------------------------+ ↓ +----------------------------+ | Hardware | +----------------------------+
The application or library can have more control over how resources are used.
Advantages
- High flexibility
- Potentially high performance
- Applications can use specialized resource-management strategies
Disadvantages
- More complex application/library design
- Less common in mainstream operating systems
Monolithic vs Microkernel
This is an important exam comparison.
| Feature | Monolithic | Microkernel |
|---|---|---|
| Kernel size | Generally large | Small |
| OS services | Many run in kernel space | Many run in user space |
| Communication | Often direct function calls | Often IPC/message passing |
| Performance | Generally high | Can have IPC overhead |
| Fault isolation | Lower | Better |
| Security | Larger trusted computing base | Smaller trusted core |
| Design | Simpler conceptually | More modular |
| Example | Linux | QNX, MINIX 3 |
Layered vs Microkernel
| Layered | Microkernel |
|---|---|
| Organizes system into layers | Minimizes kernel functionality |
| Focuses on hierarchical organization | Focuses on small kernel |
| Each layer uses lower-layer services | User-space services communicate with kernel |
| Easier conceptual structure | Better isolation for many services |
Kernel Space vs User Space
Another important concept in OS architecture is the separation between user space and kernel space.
+-----------------------------+ | USER SPACE | | | | Chrome | | VS Code | | Applications | +-----------------------------+ | System Calls ↓ +-----------------------------+ | KERNEL SPACE | | | | Process Management | | Memory Management | | File Systems | | Drivers | +-----------------------------+ | ↓ +-----------------------------+ | HARDWARE | +-----------------------------+
User Space
Applications normally execute here with restricted privileges.
Kernel Space
The kernel executes here with elevated privileges and can access protected system resources.
This separation helps prevent an ordinary application from directly modifying critical OS data or hardware state.
Example: Opening a File
Let's see how architecture works in a real situation.
Suppose you execute:
open("notes.txt")
The process can be represented as:
Application ↓ System Call ↓ Kernel ↓ File System ↓ Device Driver ↓ Storage Device
The application does not need to understand the low-level details of the storage hardware.
The OS architecture hides that complexity.
Why OS Architecture Is Important
A good architecture helps an OS achieve:
1. Performance
Efficient communication between components.
2. Security
Separating privileged and unprivileged operations.
3. Reliability
Preventing failures in one component from affecting everything else where possible.
4. Maintainability
Making components easier to modify.
5. Portability
Making it easier to adapt the OS to different hardware.
6. Scalability
Allowing the OS to support different workloads and hardware configurations.
Easy Memory Trick
Remember the architectures like this:
Monolithic → One large kernel Layered → Layers Microkernel→ Small kernel Modular → Kernel + modules Hybrid → Combination Exokernel → Expose hardware resources safely
Exam Definition
OS architecture is the internal organization and design of an operating system that defines how components such as process management, memory management, file systems, device management, and system-call interfaces are structured and communicate with each other.
Most important for exams
Focus especially on:
Monolithic → Layered → Microkernel → Modular → Hybrid