--- title: "Monolithic vs micro-kernel structure" subject: "Operating System" chapter: 1 key: "semester_6/operating_system:monolithic-vs-microkernel" source: https://www.bctengineer.com/q/semester_6/operating_system/monolithic-vs-microkernel site: BCT Engineering --- # Monolithic vs micro-kernel structure Operating System · Chapter 1: Introduction to Operating System - Asked in: 2071 Magh, 5 marks; year not given - Video: [Operating System Structures Explained | Monolithic vs Microkernel vs Hybrid | OS Design – Episode 2](https://www.youtube.com/watch?v=_OdELJ_h4pU) — BitLearn - Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14 - Page: https://www.bctengineer.com/q/semester_6/operating_system/monolithic-vs-microkernel - Whole chapter: https://www.bctengineer.com/md/semester_6/operating_system/chapter-1 ## Question Differentiate between monolithic and micro-kernel structure of an operating system. ## Short answer Monolithic kernel runs all OS services in kernel mode as a single binary with direct calls; microkernel runs minimal kernel (IPC, scheduling, memory) with services as user-mode servers using message passing. Monolithic is faster but less reliable; microkernel is more reliable, portable, and maintainable but slower. ## Answer In a **monolithic structure** the whole OS runs as one large program in kernel mode; every procedure can call any other. In a **micro-kernel structure** only a very small kernel runs in kernel mode and the remaining services run as user-mode servers that communicate by message passing. | Basis | Monolithic kernel | Micro-kernel | |---|---|---| | Structure | One large binary; all services linked together | Small core plus separate user-space servers | | Kernel size | Large | Very small | | Services in kernel mode | Process, memory, file system, drivers, networking | Only IPC, scheduling, low-level memory | | Communication | Direct procedure calls | Message passing through the kernel | | Performance | Fast, little overhead | Slower, more mode switches and copying | | Reliability | A bug in any part (e.g. a driver) can crash the whole OS | Server crash is isolated; kernel survives | | Security | Large trusted code base | Small trusted code base, easier to verify | | Maintenance / extension | Difficult; recompile the kernel | Easy; add or replace servers | | Portability | Harder | Easier (only the small kernel is hardware dependent) | | Examples | Traditional UNIX, Linux, MS-DOS | Mach, QNX, MINIX 3 | ```text Monolithic Micro-kernel +-------------+ +----+ +----+ +----+ | FS Mem Proc | | FS | |Drv | |Net | user | Drv Net ... | +----+ +----+ +----+ | (all in | +-----------------+ | kernel) | | IPC, sched, mem | kernel +-------------+ +-----------------+ ``` ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. In a monolithic OS structure, how do components communicate? A. By direct procedure calls inside one large kernel-mode program B. By message passing between user-mode servers C. Through virtual machine monitors D. Only via network sockets Answer: A. All services are linked into one binary and call each other directly. (Key point: Monolithic structure) 2. What is the effect of a faulty device driver in each structure? A. Monolithic: isolated; micro-kernel: crashes the whole OS B. Monolithic: can crash the whole OS; micro-kernel: server crash is isolated C. Both always crash the whole OS D. Neither is affected by driver bugs Answer: B. In a micro-kernel the driver is a user-mode server, so the kernel survives. (Key point: Reliability) 3. Why is a micro-kernel easier to verify for security? A. It has a larger code base running in kernel mode B. It avoids all message passing C. It has a small trusted code base D. It has no user-mode servers Answer: C. A small kernel is easier to verify than a large monolithic kernel. (Key point: Security and trusted code) 4. What is easier in a micro-kernel than in a monolithic kernel? A. Achieving the highest performance B. Calling any procedure directly C. Keeping all services in kernel mode D. Adding/replacing servers without recompiling the kernel, and porting only the small kernel Answer: D. Only the small kernel is hardware dependent and servers can be swapped. (Key point: Extension and portability) ## Related in Operating System - [Layered vs monolithic OS structure](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Alayered-vs-monolithic) — Operating System, chapter 1 - [Extended machine, kernel, system call](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Aextended-machine-kernel-syscall) — Operating System, chapter 1 - [System call; monolithic and VM architecture](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Asystem-call-architecture) — Operating System, chapter 1 - [Device controller vs kernel; DMA](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Adevice-controller-vs-kernel-dma) — Operating System, chapter 6 - [Process vs thread; user and kernel threads](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Aprocess-vs-thread-user-kernel-threads) — Operating System, chapter 2 - [File system layout; i-node vs linked list](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Afs-layout-inode-vs-linked-list) — Operating System, chapter 5 ## Related in other subjects - [Microkernel vs monolithic kernel](https://www.bctengineer.com/question.md?key=semester_7%2Fdistributed_system%3Amicrokernel-advantages) — Distributed System, chapter 3 - [Kernel and its types](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Akernel-types) — Embedded System, chapter 6, asked 2× - [File system handling of kernel](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Akernel-file-system-handling) — Embedded System, chapter 6 - [Features of a typical operating system](https://www.bctengineer.com/question.md?key=semester_4%2Fmicroprocessor%3Afeatures-of-operating-system) — Microprocessor, chapter 6, asked 3×