Wiley Professional Linux Kernel Architecture 978-0-470-34343-2 Benutzerhandbuch
Produktcode
978-0-470-34343-2
Mauerer
runc01.tex
V2 - 09/04/2008
4:13pm
Page 2
Chapter 1: Introduction and Overview
introductions ([TW06] and [Tan07]). A solid foundation of C programming is required. Because the
kernel makes use of many advanced techniques of C and, above all, of many special features of the GNU
C compiler, Appendix C discusses the finer points of C with which even good programmers may not
be familiar. A basic knowledge of computer structures will be useful as Linux necessarily interacts very
directly with system hardware — particularly with the CPU. There are also a large number of introduc-
tory works dealing with this subject; some are listed in the reference section. When I deal with CPUs
in greater depth (in most cases I take the IA-32 or AMD64 architecture as an example because Linux is
used predominantly on these system architectures), I explain the relevant hardware details. When I dis-
cuss mechanisms that are not ubiquitous in daily live, I will explain the general concept behind them,
but expect that readers will also consult the quoted manual pages for more advice on how a particular
feature is used from userspace.
kernel makes use of many advanced techniques of C and, above all, of many special features of the GNU
C compiler, Appendix C discusses the finer points of C with which even good programmers may not
be familiar. A basic knowledge of computer structures will be useful as Linux necessarily interacts very
directly with system hardware — particularly with the CPU. There are also a large number of introduc-
tory works dealing with this subject; some are listed in the reference section. When I deal with CPUs
in greater depth (in most cases I take the IA-32 or AMD64 architecture as an example because Linux is
used predominantly on these system architectures), I explain the relevant hardware details. When I dis-
cuss mechanisms that are not ubiquitous in daily live, I will explain the general concept behind them,
but expect that readers will also consult the quoted manual pages for more advice on how a particular
feature is used from userspace.
The present chapter is designed to provide an overview of the various areas of the kernel and to illustrate
their fundamental relationships before moving on to lengthier descriptions of the subsystems in the
following chapters.
their fundamental relationships before moving on to lengthier descriptions of the subsystems in the
following chapters.
Since the kernel evolves quickly, one question that naturally comes to mind is which version is cov-
ered in this book. I have chosen kernel 2.6.24, which was released at the end of January 2008. The
dynamic nature of kernel development implies that a new kernel version will be available by the time
you read this, and naturally, some details will have changed — this is unavoidable. If it were not the
case, Linux would be a dead and boring system, and chances are that you would not want to read
the book. While some of the details will have changed, concepts will not have varied essentially. This is
particularly true because 2.6.24 has seen some very fundamental changes as compared to earlier versions.
Developers do not rip out such things overnight, naturally.
ered in this book. I have chosen kernel 2.6.24, which was released at the end of January 2008. The
dynamic nature of kernel development implies that a new kernel version will be available by the time
you read this, and naturally, some details will have changed — this is unavoidable. If it were not the
case, Linux would be a dead and boring system, and chances are that you would not want to read
the book. While some of the details will have changed, concepts will not have varied essentially. This is
particularly true because 2.6.24 has seen some very fundamental changes as compared to earlier versions.
Developers do not rip out such things overnight, naturally.
1.1
Tasks of the Kernel
On a purely technical level, the kernel is an intermediary layer between the hardware and the software.
Its purpose is to pass application requests to the hardware and to act as a low-level driver to address
the devices and components of the system. Nevertheless, there are other interesting ways of viewing the
kernel.
Its purpose is to pass application requests to the hardware and to act as a low-level driver to address
the devices and components of the system. Nevertheless, there are other interesting ways of viewing the
kernel.
❑
The kernel can be regarded as an enhanced machine that, in the view of the application, abstracts
the computer on a high level. For example, when the kernel addresses a hard disk, it must decide
which path to use to copy data from disk to memory, where the data reside, which commands
must be sent to the disk via which path, and so on. Applications, on the other hand, need only
issue the command that data are to be transferred. How this is done is irrelevant to the appli-
cation — the details are abstracted by the kernel. Application programs have no contact with
the hardware itself,
the computer on a high level. For example, when the kernel addresses a hard disk, it must decide
which path to use to copy data from disk to memory, where the data reside, which commands
must be sent to the disk via which path, and so on. Applications, on the other hand, need only
issue the command that data are to be transferred. How this is done is irrelevant to the appli-
cation — the details are abstracted by the kernel. Application programs have no contact with
the hardware itself,
2
only with the kernel, which, for them, represents the lowest level in the
hierarchy they know — and is therefore an enhanced machine.
❑
Viewing the kernel as a resource manager is justified when several programs are run concurrently
on a system. In this case, the kernel is an instance that shares available resources — CPU time,
disk space, network connections, and so on — between the various system processes while at the
same time ensuring system integrity.
on a system. In this case, the kernel is an instance that shares available resources — CPU time,
disk space, network connections, and so on — between the various system processes while at the
same time ensuring system integrity.
2
The CPU is an exception since it is obviously unavoidable that programs access it. Nevertheless, the full range of possible instruc-
tions is not available for applications.
2