操作系统：螺旋进阶教程

需积分: 9 160 浏览量更新于2024-07-17 收藏 7.61MB PDF 举报

"Operating Systems: A Spiral Approach 是一本由Ramez Elmasri、A. Gil Carrick和David Levine合著的操作系统教程，采用螺旋方法进行讲解，全书共546页，属于计算机科学丛书系列。这本书由McGraw-Hill出版，版权归属2010年的The McGraw-Hill Companies, Inc.。" 本书的核心概念是“螺旋方法”，这是一种系统设计和开发的方法论，强调在开发过程中反复迭代和逐步细化。在操作系统的设计和实现中，螺旋方法特别适合，因为它考虑了风险分析和用户反馈，确保在每个阶段都对项目有更深入的理解和控制。操作系统作为计算机科学中的核心主题，本书涵盖了以下关键知识点： 1. **操作系统概述**：介绍操作系统的定义、功能和类型，包括批处理、分时、实时、网络和分布式操作系统等。 2. **进程管理**：详细讲解进程的概念、状态转换、进程调度、同步与通信机制，如信号量、管程、消息传递等。 3. **内存管理**：阐述内存组织、地址映射、内存分配与回收、页面替换算法以及虚拟内存原理。 4. **文件系统**：探讨文件的组织、存储、访问控制，以及文件系统的实现，包括目录结构和磁盘调度。 5. **输入/输出（I/O）管理**：介绍I/O设备、中断、DMA（直接存储器访问）、I/O控制器以及缓冲技术。 6. **处理器调度**：详细解析不同调度策略，如先来先服务、短作业优先、时间片轮转等，以及它们在不同环境下的应用。 7. **死锁预防与避免**：讨论死锁的概念、条件、检测和预防策略，如资源预分配、银行家算法等。 8. **安全性与保护**：涵盖访问控制、权限管理、防火墙、加密技术以及安全模型。 9. **分布式系统**：介绍分布式操作系统的架构、通信协议、容错机制以及并行计算。 10. **风险分析**：螺旋方法中的一个重要环节，书中可能会涉及如何识别和评估项目中的潜在风险，并制定相应的应对策略。通过螺旋方法，读者可以逐步深入理解操作系统的复杂性，每次迭代都增加了新的细节和理解，从而形成对整个系统的全面认识。该书不仅适合计算机科学专业的学生学习，也适用于软件工程师和系统管理员提升其在操作系统领域的专业技能。

Confirming Pages

In this part:

Chapter 1: Getting Started 3

Chapter 2: Operating System Concepts, Components,

and Architectures 19

his part of the book contains two chapters. Chapter 1 gives a basic explanation

about what an Operating System (or OS for short) is. It explains how the OS

provides services to users and programmers. These services make it possible

to utilize a computer without having to deal with the low-level, arcane details, but

rather, being allowed to concentrate on the problem(s) to be solved. Such problems

may be anything, including not only the things we normally consider computing

activities, but also activities such as playing games, dynamically generating art, and

monitoring the performance of an automobile engine.

Chapter 2 provides an initial high-level look at OS concepts, components, and

architecture. General terms are introduced that a student will need to know in order to

study the series of increasingly more complex OSs that are presented in Part 2.

Operating Systems Overview

and Background

Part Part

1 1

elm49810_ch01_001-018.indd 1elm49810_ch01_001-018.indd 1 12/10/08 10:15:47 PM12/10/08 10:15:47 PM

Confirming Pages

Chapter Chapter

1 1

Getting Started

In this chapter:

1.1 Introduction 4

1.2 What Are Operating Systems All About? 5

1.3 User versus System View of an OS 6

1.4 Some OS Terms, Basic Concepts, and Illustrations 10

1.5 A Small Historical Diversion 15

1.6 Summary 17

perating systems are at the heart of every computer. The Operating System

(or OS for short) provides services to users and programmers that make it

possible to utilize a computer without having to deal with the low-level, dif-

ficult-to-use hardware commands. It provides relatively uniform interfaces to access

the extremely wide variety of devices that a computer interacts with, from input/

output devices such as printers and digital cameras, to wired and wireless network

components that allow computers to communicate. It allows users to create, manage,

and organize different types of files. In addition, most modern OSs provide graphical

user interfaces (GUIs) to allow a relatively easy-to-use interface for computer users.

In this opening chapter, we start in Section 1.1 with a brief introduction to

show how important an Operating System is and how they are used not only in

computers but also in many types of electronic devices that we all use in our

daily routines. Section 1.2 is a more technical look at why even simple devices

contain an Operating System. Then in Section 1.3 we discuss the different views

of what an Operating System does by looking at the Operating System from two

perspectives: the user’s perspective and the system’s perspective. We also discuss

the requirements that each type of user has for the Operating System. Section 1.3

next gives a few simple examples to illustrate some sequences of functions that

an Operating System goes through to perform seemingly simple user requests.

In Section 1.4 we present some basic terminology and concepts, and give some

figures to illustrate typical components for a simple Operating System. We give a

brief historical perspective in Section 1.5 and conclude with a chapter summary

in Section 1.6 .

elm49810_ch01_001-018.indd 3elm49810_ch01_001-018.indd 3 12/10/08 10:15:48 PM12/10/08 10:15:48 PM

Confirming Pages

4 Part 1 Operating Systems Overview and Background

1.1 INTRODUCTION

For many years, OSs were viewed by most people as uninteresting—except for

OS programmers and computer “nerds.” Because of a number of high-profile cases,

OSs have occasionally become front-page news in recent years. Suddenly, the OS

is seen by some as controlling all computing. There are very strongly felt opinions

about what constitutes good versus bad OSs. There is also quite a bit of disagree-

ment about what functionality should be provided by the OS. While many people

(and some courts!) believe that one company dominates the OS market, others say

that the OS is increasingly unimportant—the Internet browser is the OS. In fact,

there is a very wide variety of types of OSs, and OSs exist at some level on every

conceivable computing device, including some that may surprise many people.

For example, handheld personal digital assistants ( PDA s) have very capable,

complex, and flexible OSs. Most electronic devices that have some intelligence

have complex, yet easy-to-use OSs and system software to control them. The OS

that was once thought of as the arcane world of process management and memory

management techniques is now occasionally a conversation topic in cafés, bars,

and computer stores. Many people now seem to be experts—or at least have an

opinion—on OSs.

(Perhaps) Surprising places to find an OS:

Personal digital assistants

Cable TV controller boxes

Electronic games

Copiers

Fax machines

Remote controls

Cellular telephones

Automobile engines

Digital cameras

While we also have our opinions, we try to get behind the hype—generated

by marketing and salespeople as well as millions of opinionated users—in order

to explain the real systems. We also throw in our own opinions when needed and

explain why we hold these beliefs. We give many examples of currently used sys-

tems to demonstrate concepts and show what is good and bad about the various sys-

tems. We try to avoid the so-called religious issues, such as: Which is the better OS:

Windows or Mac-OS? Or are UNIX and its variations such as Linux better than

both? Instead, we point out how these systems came about and what they provide to

users and programmers.

elm49810_ch01_001-018.indd 4elm49810_ch01_001-018.indd 4 12/10/08 10:15:53 PM12/10/08 10:15:53 PM

Confirming Pages

Chapter 1 Getting Started 5

Increasingly, certain parts of the OS—particularly those handling user and

application program interaction—are visible to users and programmers and often

may be critical in marketing a computer or electronic—or even mechanical—

device. Buyers are becoming very critical and have higher expectations of what the

OS should provide them. More than ever before, the system must not only provide

new features and be easier to use but it must also support those old features and

applications that we are used to. Of course, as we add new devices—video devices

and disks, high fidelity sound, and wireless networking, for example—we want the

system to easily adapt to and handle those devices. In fact, a good OS architecture

should even allow the connection of new devices that were not yet available and

may not even have been thought of when the OS was created!

1.2 WHAT ARE OPERATING SYSTEMS ALL ABOUT?

In this section, we give a simple example—a simple handheld game system—to

illustrate some of the basic functionalities that an OS should provide.

Think about a handheld electronic game system, one that is very cheap but has a

small screen, a few buttons, and several games. Although this game system might not

require an OS, it probably has one. The main reason is to consolidate the common

functions needed by the various games installed on the game system.

The games typically have some common parts. For example, each game needs to

get some input from the buttons, and to display something on the screen. While those

actions sound easy, they do require some not-so-simple software programming. Get-

ting the input from a button—that sounds easy. Well, except that the user may push two

buttons at once—what then? It is also likely that a cheap game does not use sophis-

ticated and expensive buttons, so there is electronic noise that may distort the signal

coming in—how should the games deal with that? The easy solution is to handle each

of these common issues in one, single place. For example, all button pushes can be read

in, have any noise cleaned up, and so forth in a single software routine. Having a single

read-the-button software routine has the advantage of providing a consistent user inter-

face—all games treat button input in the same way. It also allows the routine to occupy

space in only one place in system memory instead of occupying space in each individ-

ual game. And where should that read-the-button software routine be placed? It should

be in the OS—where every game that needs to read a button can call this routine.

The OS should also handle unexpected events. For example, a user may quit a

game in the middle (when losing) and start another game. No reboot of the game sys-

tem should be necessary. The user’s need to switch from game to game (task to task)

is natural and expected. In fact, users (5-year-olds) may push buttons at unexpected

times and the screen should continue to be updated (refreshed) while the game is being

played—even while waiting for a button to be pushed. This is called asynchronicity,

which can be defined informally as the occurrence of events at random or unexpected

times—a very important feature in even simple systems like a handheld game.

Several important OS concepts are part of this game system: When a game is

started, some part of its software may be loaded into memory, whereas other parts

elm49810_ch01_001-018.indd 5elm49810_ch01_001-018.indd 5 12/10/08 10:15:53 PM12/10/08 10:15:53 PM

剩余545页未读，继续阅读

depiero1229

粉丝: 0
资源: 4

操作系统：螺旋进阶教程

操作系统实用教程.pdf

spiral_search() missing 1 required positional argument: 'dsm'

pycharm安装spiral库失败

螺旋矩阵python

Spiral-STC算法

fibonacci spiral gridpoints on a sphere

机器人在线覆盖 Spiral-STC算法 python

机器人 Spiral-STC算法

机器人在线覆盖 Spiral-STC算法

最新资源