Operating Systems/Kernel Models

From Wikiversity

Contents 1 Introduction 2 Monolithic Kernel 2.1 Design 2.1.1 Pros 2.1.2 Cons 2.2 Examples 3 Microkernel 3.1 Design 3.1.1 Pros 3.1.2 Cons 3.2 Examples 4 Hybrid kernel 4.1 Design 4.2 Examples

[edit] Introduction

The kernel is the name given to the program that does most of the housekeeping tasks for the operating system. The boot loader hands control over to the kernel, which initializes the various devices to a known state and makes the computer ready for general operation.

After preparing the hardware for use, the kernel provides an abstraction layer between the hardware and software running on the system. Through an API, or application programming interface, software can request the kernel to perform hardware tasks, as well as access many common functions. Most current kernels also multi-task the hardware, sharing it between the various processes running on the system.

[edit] Monolithic Kernel

[edit] Design

Monolithic Kernels function with all of the kernel and device drivers inside one address space running in kernel mode. The principle advantage to this approach is efficiency (especially on x86 architectures where a task switch is a particularly expensive operation). Unfortunately, monolithic kernels suffer the risk of the entire system crashing due to a bug in a device driver.

[edit] Pros

• Speed
• Simplicity of design

[edit] Cons

• Potential stability issues
• Can become huge - Linux 2.6 has 7.0 million lines of code
• Potentially difficult to maintain

[edit] Examples

• Traditional Unix kernels (includes BSDs and Solaris)
• Linux
• MS-DOS, Windows 9x
• Mac OS versions below 8.6

[edit] Microkernel

[edit] Design

A Microkernel tries to run most of its services and device drivers in userspace. This can result in an increase in stability and possibly security on machines with an Memory Management Unit.

[edit] Pros

• Stability
• Security
• Potentially more responsive (though often not in practice)
• Benefits for SMP machines

[edit] Cons

• Additional context switches are usually required
• Slow Inter Process Communication can result in poor performance

[edit] Examples

• AmigaOS
• Amoeba
• Mach
• Minix
• L4
• QNX

[edit] Hybrid kernel

[edit] Design

A hybrid kernel combines the concepts of both monolithic kernels and microkernels. It is generally implemented by having a monolithic kernel with a more microkernel like design. When properly implemented it is hoped that this will result in the performance benefits of a monolithic kernel, with the stability of a Microkernel

[edit] Examples

• NT kernel (also used in 2000, XP, and vista)
• Darwin (Mac OS X's kernel)
• DragonFly BSD
• BeOS
• Plan 9