How to Master the Linux Kernel: A Practical Study Blueprint

Why Write This Blog

When you start learning the kernel, avoid focusing on a single subsystem and diving straight into low‑level code, because you will encounter many intertwined data structures and global variables that make the code appear chaotic and overwhelming.

Understanding each subsystem’s design philosophy first gives you a clearer, forest‑view perspective, preventing frustration and scattered attention.

My Learning Method

Initially, the challenge is to know that something exists rather than fully understand it. Build a mental framework of the kernel’s major subsystems and their design ideas, then identify the high‑level “main” functions that embody those ideas.

Use LKD3 as the primary reference; it discusses concepts, designs, and major implementation methods without delving deeply into individual function code. Complement it with ULK3 and PLKA , which provide alternative viewpoints and deeper analysis of the same subsystems.

Read the three books in parallel: first grasp the design principles with LKD3, then skim ULK3 and PLKA for additional insights, returning to the code only when a particular point remains unclear.

Language

PLKA was originally written in German, translated to English and then to Chinese; ULK3 and LKD3 are available in English. Reading the original English versions is recommended for programmers.

API Thoughts

Kernel APIs differ from application APIs: they must be portable across platforms and are heavily standardized. Understanding the underlying OS implementation helps you choose the most efficient API usage in application development.

Design Essence: Knowing vs. Understanding

The OS sits between hardware and applications; its subsystems depend on hardware characteristics. Knowing why a design is organized a certain way (the “why”) complements knowing what it does (the “what”).

For example, interrupt handling in ULK3 follows Intel x86 architecture, and time‑timer management aligns with Intel V3’s APIC description.

Hands‑On Coding

Reading alone is insufficient; you must compile and run kernel modules, use UML for debugging, and step through code to solidify understanding.

References

LDD3 – Linux Device Drivers 3rd

LKD3 – Linux Kernel Development 3rd

ULK3 – Understanding the Linux Kernel 3rd

PLKA – Professional Linux Kernel Architecture

UML – User Mode Linux

Intel V3 – Intel 64 and IA‑32 Architectures Software Developer’s Manual Volume 3

Conclusion

Passion fuels learning; combining interest with disciplined study and practical experimentation turns Linux kernel exploration into both a skill and a rewarding experience.