深入理解Linux内核：Ubuntu, Fedora, SUSE与最新IT资讯

需积分: 9 168 浏览量更新于2024-07-24 收藏 3.81MB PDF 举报

"Understanding the Linux Kernel" 是一本由Daniel P. Bovet和Marco Cesati编写的书籍，由O'Reilly出版社出版，首次发行于2000年10月，共702页。这本书旨在帮助读者理解Linux内核如何高效运行以及如何适应各种不同的环境。作者通过解释每个主题的重要性，展示内核操作与Unix程序员和用户熟悉的工具之间的关系。 Linux内核是Linux操作系统的核心，负责管理系统的硬件资源，如处理器、内存、磁盘驱动器等，并为上层的应用程序提供服务。在"Understanding the Linux Kernel"一书中，作者深入探讨了以下几个关键领域： 1. **进程管理**：包括进程创建、调度、同步、通信以及进程间的信号传递。这有助于理解如何控制和管理多个执行单元在系统上的并发运行。 2. **内存管理**：讲解了虚拟内存系统、页面缓存、交换机制以及内存分配策略，这些是优化系统性能和资源利用率的关键。 3. **文件系统**：涵盖了Linux支持的各种文件系统类型，如EXT2, EXT3, EXT4, XFS等，以及它们如何存储和检索数据。 4. **网络协议栈**：讨论了TCP/IP协议族的工作原理，包括网络接口层、IP层、传输层（TCP和UDP）以及套接字编程接口。 5. **设备驱动程序**：解释了如何与硬件交互，以及如何编写和理解内核中的驱动程序代码，这对于定制硬件支持至关重要。 6. **中断处理和定时器**：阐述了中断如何在硬件事件发生时暂停当前进程并执行特定的服务，以及定时器如何用于计划任务和保持系统时钟。 7. **系统调用**：描述了用户空间与内核空间的交互方式，即通过系统调用接口来执行特权级操作。 8. **安全性与权限**：分析了Linux的用户和组概念，以及访问控制列表（ACL）、能力系统（capabilities）和安全模块（如SELinux）在保护系统资源方面的作用。 9. **内核配置与编译**：介绍了如何根据特定需求定制内核，包括选择要包含的功能和优化选项。 "Understanding the Linux Kernel"不仅适合Linux开发者和系统管理员，也对任何希望深入了解操作系统工作原理的读者有极大的价值。书中的实例和清晰的解释可以帮助读者将理论知识应用到实际问题解决中，提升对Linux内核的实践操作能力。 Linux公社（LinuxIDC.com）是一个专注于Linux技术的网站，提供了Ubuntu、Fedora、SUSE等不同Linux发行版的技术资料，同时也更新最新的IT资讯，为Linux爱好者和专业人士提供了一个交流和学习的平台。该网站还设有多个专题栏目，如Ubuntu、Fedora、Red Hat、SUSE和Android，以满足不同用户群体的需求。

Understanding the Linux Kernel

Linux is fully customizable in all its components.

Thanks to the General Public License (GPL), you are allowed to freely read and

modify the source code of the kernel and of all system programs.

[3]

Several commercial companies have started to support their products under Linux, most of which aren't distributed under a GNU Public License.

Therefore, you may not be allowed to read or modify their source code.

Linux runs on low-end, cheap hardware platforms.

You can even build a network server using an old Intel 80386 system with 4 MB of

RAM.

Linux is powerful.

Linux systems are very fast, since they fully exploit the features of the hardware

components. The main Linux target is efficiency, and indeed many design choices of

commercial variants, like the STREAMS I/O subsystem, have been rejected by Linus

because of their implied performance penalty.

Linux has a high standard for source code quality.

Linux systems are usually very stable; they have a very low failure rate and system

maintenance time.

The Linux kernel can be very small and compact.

Indeed, it is possible to fit both a kernel image and full root filesystem, including all

fundamental system programs, on just one 1.4 MB floppy disk! As far as we know,

none of the commercial Unix variants is able to boot from a single floppy disk.

Linux is highly compatible with many common operating systems.

It lets you directly mount filesystems for all versions of MS-DOS and MS Windows,

SVR4, OS/2, Mac OS, Solaris, SunOS, NeXTSTEP, many BSD variants, and so on.

Linux is also able to operate with many network layers like Ethernet, Fiber Distributed

Data Interface (FDDI), High Performance Parallel Interface (HIPPI), IBM's Token

Ring, AT&T WaveLAN, DEC RoamAbout DS, and so forth. By using suitable

libraries, Linux systems are even able to directly run programs written for other

operating systems. For example, Linux is able to execute applications written for MS-

DOS, MS Windows, SVR3 and R4, 4.4BSD, SCO Unix, XENIX, and others on the

Intel 80x86 platform.

Linux is well supported.

Believe it or not, it may be a lot easier to get patches and updates for Linux than for

any proprietary operating system! The answer to a problem often comes back within

a few hours after sending a message to some newsgroup or mailing list. Moreover,

drivers for Linux are usually available a few weeks after new hardware products have

been introduced on the market. By contrast, hardware manufacturers release device

drivers for only a few commercial operating systems, usually the Microsoft ones.

www.linuxidc.com

Linux公社(LinuxIDC.com) 是包括Ubuntu,Fedora,SUSE技术，最新IT资讯等Linux专业类网站。

Understanding the Linux Kernel

s390

IBM System/390 mainframes

1.3 Linux Versions

Linux distinguishes stable kernels from development kernels through a simple numbering

scheme. Each version is characterized by three numbers, separated by periods. The first two

numbers are used to identify the version; the third number identifies the release.

As shown in Figure 1-1, if the second number is even, it denotes a stable kernel; otherwise, it

denotes a development kernel. At the time of this writing, the current stable version of the

Linux kernel is 2.2.14, and the current development version is 2.3.51. The 2.2 kernel, which is

the basis for this book, was first released in January 1999, and it differs considerably from the

2.0 kernel, particularly with respect to memory management. Work on the 2.3 development

version started in May 1999.

Figure 1-1. Numbering Linux versions

New releases of a stable version come out mostly to fix bugs reported by users. The main

algorithms and data structures used to implement the kernel are left unchanged.

Development versions, on the other hand, may differ quite significantly from one another;

kernel developers are free to experiment with different solutions that occasionally lead to

drastic kernel changes. Users who rely on development versions for running applications may

experience unpleasant surprises when upgrading their kernel to a newer release. This book

concentrates on the most recent stable kernel that we had available because, among all

the new features being tried in experimental kernels, there's no way of telling which will

ultimately be accepted and what they'll look like in their final form.

At the time of this writing, Linux 2.4 has not officially come out. We tried to anticipate the

forthcoming features and the main kernel changes with respect to the 2.2 version by looking

at the Linux 2.3.99-pre8 prerelease. Linux 2.4 inherits a good deal from Linux 2.2: many

concepts, design choices, algorithms, and data structures remain the same. For that reason, we

conclude each chapter by sketching how Linux 2.4 differs from Linux 2.2 with respect to

the topics just discussed. As you'll notice, the new Linux is gleaming and shining; it should

appear more appealing to large corporations and, more generally, to the whole business

community.

www.linuxidc.com

Linux公社(LinuxIDC.com) 是包括Ubuntu,Fedora,SUSE技术，最新IT资讯等Linux专业类网站。

Understanding the Linux Kernel

1.4 Basic Operating System Concepts

Any computer system includes a basic set of programs called the operating system. The most

important program in the set is called the kernel. It is loaded into RAM when the system boots

and contains many critical procedures that are needed for the system to operate. The other

programs are less crucial utilities; they can provide a wide variety of interactive experiences

for the user—as well as doing all the jobs the user bought the computer for—but the essential

shape and capabilities of the system are determined by the kernel. The kernel, then, is where

we fix our attention in this book. Hence, we'll often use the term "operating system" as

a synonym for "kernel."

The operating system must fulfill two main objectives:

• Interact with the hardware components servicing all low-level programmable elements

included in the hardware platform.

• Provide an execution environment to the applications that run on the computer system

(the so-called user programs).

Some operating systems allow all user programs to directly play with the hardware

components (a typical example is MS-DOS). In contrast, a Unix-like operating system hides

all low-level details concerning the physical organization of the computer from applications

run by the user. When a program wants to make use of a hardware resource, it must issue

a request to the operating system. The kernel evaluates the request and, if it chooses to grant

the resource, interacts with the relative hardware components on behalf of the user program.

In order to enforce this mechanism, modern operating systems rely on the availability of

specific hardware features that forbid user programs to directly interact with low-level

hardware components or to access arbitrary memory locations. In particular, the hardware

introduces at least two different execution modes for the CPU: a nonprivileged mode for user

programs and a privileged mode for the kernel. Unix calls these User Mode and Kernel Mode,

respectively.

In the rest of this chapter, we introduce the basic concepts that have motivated the design of

Unix over the past two decades, as well as Linux and other operating systems. While the

concepts are probably familiar to you as a Linux user, these sections try to delve into them

a bit more deeply than usual to explain the requirements they place on an operating system

kernel. These broad considerations refer to Unix-like systems, thus also to Linux. The other

chapters of this book will hopefully help you to understand the Linux kernel internals.

1.4.1 Multiuser Systems

A multiuser system is a computer that is able to concurrently and independently execute

several applications belonging to two or more users. "Concurrently" means that applications

can be active at the same time and contend for the various resources such as CPU, memory,

hard disks, and so on. "Independently" means that each application can perform its task with

no concern for what the applications of the other users are doing. Switching from one

application to another, of course, slows down each of them and affects the response time seen

by the users. Many of the complexities of modern operating system kernels, which we will

examine in this book, are present to minimize the delays enforced on each program and to

provide the user with responses that are as fast as possible.

www.linuxidc.com

Linux公社(LinuxIDC.com) 是包括Ubuntu,Fedora,SUSE技术，最新IT资讯等Linux专业类网站。

Understanding the Linux Kernel

Multiuser operating systems must include several features:

• An authentication mechanism for verifying the user identity

• A protection mechanism against buggy user programs that could block other

applications running in the system

• A protection mechanism against malicious user programs that could interfere with, or

spy on, the activity of other users

• An accounting mechanism that limits the amount of resource units assigned to each

user

In order to ensure safe protection mechanisms, operating systems must make use of the

hardware protection associated with the CPU privileged mode. Otherwise, a user program

would be able to directly access the system circuitry and overcome the imposed bounds. Unix

is a multiuser system that enforces the hardware protection of system resources.

1.4.2 Users and Groups

In a multiuser system, each user has a private space on the machine: typically, he owns some

quota of the disk space to store files, receives private mail messages, and so on. The operating

system must ensure that the private portion of a user space is visible only to its owner. In

particular, it must ensure that no user can exploit a system application for the purpose of

violating the private space of another user.

All users are identified by a unique number called the User ID , or UID. Usually only a

restricted number of persons are allowed to make use of a computer system. When one of

these users starts a working session, the operating system asks for a login name and a

password. If the user does not input a valid pair, the system denies access. Since the password

is assumed to be secret, the user's privacy is ensured.

In order to selectively share material with other users, each user is a member of one or more

groups, which are identified by a unique number called a Group ID , or GID. Each file is also

associated with exactly one group. For example, access could be set so that the user owning

the file has read and write privileges, the group has read-only privileges, and other users on

the system are denied access to the file.

Any Unix-like operating system has a special user called root, superuser, or supervisor. The

system administrator must log in as root in order to handle user accounts, perform

maintenance tasks like system backups and program upgrades, and so on. The root user can

do almost everything, since the operating system does not apply the usual protection

mechanisms to her. In particular, the root user can access every file on the system and can

interfere with the activity of every running user program.

1.4.3 Processes

All operating systems make use of one fundamental abstraction: the process . A process can

be defined either as "an instance of a program in execution," or as the "execution context" of a

running program. In traditional operating systems, a process executes a single sequence of

instructions in an address space ; the address space is the set of memory addresses that the

process is allowed to reference. Modern operating systems allow processes with multiple

www.linuxidc.com

Linux公社(LinuxIDC.com) 是包括Ubuntu,Fedora,SUSE技术，最新IT资讯等Linux专业类网站。

剩余542页未读，继续阅读

Daemon_1994

粉丝: 94
资源: 1

深入理解Linux内核：Ubuntu, Fedora, SUSE与最新IT资讯

Linux Kernel：探索早期PC硬件基础与Linux发展渊源

Linux Kernel核心原理图解手册

深入理解Linux Kernel：中文权威指南

linux kernel

linux Kernel

Linux kernel Architecture+Understanding Linux kernel

linux_kernel_map.rar_Linux kernel m_Linux kernel map_linux ker

The Linux Kernel API.rar_Kernel_The Linux Kernel API_linux kern

Linux-kernel-architecture.zip_linux_linux kernel_linux-kernel_li

linux kernel 三本经典内核书籍+linux kernel api+linux device model

最新资源