程序员视角解析：深入理解计算机系统运作原理

5星 · 超过95%的资源需积分: 9 79 浏览量更新于2024-08-02 收藏 4.7MB PDF 举报

"《计算机系统：程序员视角》（Computer Systems: A Programmer's Perspective, Beta Draft）是一本深入解析计算机系统工作原理的书籍，作者是Randal E. Bryant和David R. O'Hallaron，出版日期为2001年11月16日。本书从程序员的角度出发，详细讲解了计算机如何运行和执行程序，帮助读者建立起对底层系统运作的全面理解。首先，章节1介绍了计算机系统的基础概念。信息在计算机中是以二进制位的形式存在，并且以上下文的方式进行处理（1.1）。程序则是通过其他程序的编译或解释转换成不同的形式，这对于理解编译系统的工作至关重要（1.2）。处理器的核心职责是读取内存中的指令并执行它们，硬件组织（如CPU、内存、I/O设备等）直接影响到程序的运行效率（1.4）。书中强调了缓存（1.5）的作用，缓存能够加快数据访问速度，提高性能。存储设备被组织成一个层次结构，从高速的寄存器到较慢的硬盘，每个层次都有其特定的用途（1.6）。操作系统作为硬件管理的关键组件，负责进程的调度、线程的管理、虚拟内存的分配以及文件系统操作（1.7）。网络通信也是计算机系统的重要组成部分，系统之间通过网络进行数据交换和通信（1.8）。接下来，第二部分着重于程序的结构和执行过程，探讨了信息的表示与操作方式，包括数据存储的不同形式、十六进制表示、字节序、字符串的表示等（2.1至2.1.6）。这本书不仅提供了理论知识，而且通过实例，如运行'hello'程序来直观展示这些概念在实际操作中的应用。对于想要深入理解计算机系统的程序员来说，这是一本不可或缺的参考书，它帮助读者建立起扎实的理论基础，提升编程技能和问题解决能力。"

CONTENTS

Preface

This book is for programmers who want to improve their skills by learning about what is going on “under

the hood” of a computer system. Our aim is to explain the important and enduring concepts underlying all

computer systems, and to show you the concrete ways that these ideas affect the correctness, performance,

and utility of your application programs. By studying this book, you will gain some insights that have

immediate value to you as a programmer, and others that will prepare you for advanced courses in compilers,

computer architecture, operating systems, and networking.

The book owes its origins to an introductory course that we developed at Carnegie Mellon in the Fall of

1998, called 15-213: Introduction to Computer Systems. The course has been taught every semester since

then, each time to about 150 students, mostly sophomores in computer science and computer engineering.

It has become a prerequisite for all upper-level systems courses. The approach is concrete and hands-on.

Because of this, we are able to couple the lectures with programming labs and assignments that are fun and

exciting.

The response from our students and faculty colleagues was so overwhelming that we decided that others

might beneﬁt from our approach. Hence the book. This is the Beta draft of the manuscript. The ﬁnal

hard-cover version will be available from the publisher in Summer, 2002, for adoption in the Fall, 2002

term.

Assumptions About the Reader’s Background

This course is based on Intel-compatible processors (called “IA32” by Intel and “x86” colloquially) running

C programs on the Unix operating system. The text contains numerous programming examples that have

been compiled and run under Unix. We assume that you have access to such a machine, and are able to log

in and do simple things such as changing directories. Even if you don’t use Linux, much of the material

applies to other systems as well. Intel-compatible processors running one of the Windows operating systems

use the same instruction set, and support many of the same programming libraries. By getting a copy of the

Cygwin tools (http://cygwin.com/), you can set up a Unix-like shell under Windows and have an

environment very close to that provided by Unix.

We also assume that you have some familiarity with C or C++. If your only prior experience is with Java,

the transition will require more effort on your part, but we will help you. Java and C share similar syntax

and control statements. However, there are aspects of C, particularly pointers, explicit dynamic memory

allocation, and formatted I/O, that do not exist in Java. The good news is that C is a small language, and it

PREFACE

is clearly and beautifully described in the classic “K&R” text by Brian Kernighan and Dennis Ritchie [37].

Regardless of your programming background, consider K&R an essential part of your personal library.

New to C?

To help readers whose background in C programming is weak (or nonexistent), we have included these special notes

to highlight features that are especially important in C. We assume you are familiar with C++ or Java. End

Several of the early chapters in our book explore the interactions between C programs and their machine-

language counterparts. The machine language examples were all generated by the GNU

GCC compiler

running on an Intel IA32 processor. We do not assume any prior experience with hardware, machine lan-

guage, or assembly-language programming.

How to Read This Book

Learning how computer systems work from a programmer’s perspective is great fun, mainly because it can

be done so actively. Whenever you learn some new thing, you can try it out right away and see the result

ﬁrst hand. In fact, we believe that the only way to learn systems is to do systems, either working concrete

problems, or writing and running programs on real systems.

This theme pervades the entire book. When a new concept is introduced, it is followed in the text by one

or more Practice Problems that you should work immediately to test your understanding. Solutions to

the Practice Problems are at the back of the book. As you read, try to solve each problem on your own,

and then check the solution to make sure you’re on the right track. Each chapter is followed by a set of

Homework Problems of varying difﬁculty. Your instructor has the solutions to the Homework Problems in

an Instructor’s Manual. Each Homework Problem is classiﬁed according to how much work it will be:

Category 1: Simple, quick problem to try out some idea in the book.

Category 2: Requires 5–15 minutes to complete, perhaps involving writing or running programs.

Category 3: A sustained problem that might require hours to complete.

Category 4: A laboratory assignment that might take one or two weeks to complete.

Each code example in the text was formatted directly, without any manual intervention, from a C program

compiled with

GCC version 2.95.3, and tested on a Linux system with a 2.2.16 kernel. The programs are

available from our Web page at www.cs.cmu.edu/˜ics.

The ﬁle names of the larger programs are documented in horizontal bars that surround the formatted code.

For example, the program

iii

code/intro/hello.c

1 #include <stdio.h>

int main()

4 {

5 printf("hello, world\n");

6 }

code/intro/hello.c

can be found in the ﬁle hello.c in directory code/intro/. We strongly encourage you to try running

the example programs on your system as you encounter them.

There are various places in the book where we show you how to run programs on Unix systems:

unix>

./hello

hello, world

unix>

In all of our examples, the output is displayed in a roman font, and the input that you type is displayed in

an italicized font. In this particular example, the Unix shell program prints a command-line prompt and

waits for you to type something. After you type the string “./hello” and hit the return or enter

key, the shell loads and runs the hello program from the current directory. The program prints the string

“hello, world\n” and terminates. Afterwards, the shell prints another prompt and waits for the next

command. The vast majority of our examples do not depend on any particular version of Unix, and we

indicate this independence with the generic “unix>” prompt. In the rare cases where we need to make a

point about a particular version of Unix such as Linux or Solaris, we include its name in the command-line

prompt.

Finally, some sections (denoted by a “*”) contain material that you might ﬁnd interesting, but that can be

skipped without any loss of continuity.

Acknowledgements

We are deeply indebted to many friends and colleagues for their thoughtful criticisms and encouragement. A

special thanks to our 15-213 students, whose infectious energy and enthusiasm spurred us on. Nick Carter

and Vinny Furia generously provided their malloc package. Chris Lee, Mathilde Pignol, and Zia Khan

identiﬁed typos in early drafts.

Guy Blelloch, Bruce Maggs, and Todd Mowry taught the course over multiple semesters, gave us encour-

agement, and helped improve the course material. Herb Derby provided early spiritual guidance and encour-

agement. Allan Fisher, Garth Gibson, Thomas Gross, Satya, Peter Steenkiste, and Hui Zhang encouraged

us to develop the course from the start. A suggestion from Garth early on got the whole ball rolling, and this

was picked up and reﬁned with the help of a group led by Allan Fisher. Mark Stehlik and Peter Lee have

been very supportive about building this material into the undergraduate curriculum. Greg Kesden provided

剩余782页未读，继续阅读

hangshin

粉丝: 1
资源: 4

程序员视角解析：深入理解计算机系统运作原理

P802.11ax-D8.0-Draft.pdf

OCP_NIC_3.0_d1v11_20210719c_TN_CB_DRAFT.pdf

基于Draft.js自定义富文本编辑器

Package pdftex.def Error: File `fig1-eps-converted-to.pdf' not found: using draft setting. \includegraphics[width=\textwidth]{fig1.eps}

如何修改Draft.js中ContentState的blockMap

draft-js使用

Package pdftex.def:File fig1-eps-converted-to.pdf not found:using draft setting

Package pdftex.def Error: File `fig1-eps-converted-to.pdf' not found: using draft setting.

draft-js-import-markdown

最新资源