Monolithic Kernel
Subject: Computer and Technology noun /ˌmɑː.nəˈlɪθ.ɪk ˈkɜːr.nəl/ 1 definition
- operating-systems
- systems-architecture
- kernel-design
- computer-science
-
Definition (noun)
Entry #211 · UpdatedA Monolithic Kernel is an operating system architecture in which all core system services—including process scheduling, memory management, file systems, network stacks, and device drivers—execute within a single shared address space in privileged kernel mode. Rather than isolating services into separate user-space server processes like a microkernel, it maintains a single hardware-enforced boundary between user applications and the kernel via system calls, allowing internal subsystems to communicate directly through function calls and shared memory. This unified model minimizes context-switching and message-passing overhead for high runtime throughput, though it expands the trusted computing base so that a critical fault in any driver or subsystem can crash the entire system.
Common Forms
Static Monolithic Kernel: Compiles all core subsystems and device drivers into a single fixed binary image at build time, requiring a full rebuild and reboot to add or update components (characteristic of early Unix releases).
Modular Monolithic Kernel: Executes all active components in one privileged address space while supporting dynamically loadable kernel modules, allowing drivers and file systems to be inserted or removed at runtime without rebooting (used by modern Linux and BSD systems).
Preemptible Monolithic Kernel: Permits the scheduler to interrupt an in-progress kernel-mode thread so a higher-priority task can run immediately, lowering dispatch latency for interactive and real-time workloads compared to non-preemptible kernels.
Example
When an application on a Linux server issues a
read()system call on an NVMe-backed ext4 file, execution traps once into the monolithic kernel and traverses the virtual file system, ext4 driver, block layer, and NVMe driver via direct in-memory function calls without inter-process message passing. Because those components share one privileged address space, however, a null-pointer dereference in a buggy third-party storage driver triggers a kernel panic that brings down the entire host.