56
Chapter 2: Operating-System Chapter 2: Operating-System Structures Structures

Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

Embed Size (px)

Citation preview

Page 1: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

Chapter 2: Operating-System StructuresChapter 2: Operating-System Structures

Page 2: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.2/56

Chapter 2: Operating-System StructuresChapter 2: Operating-System Structures

Operating System Services

User Operating System Interface

System Calls

Types of System Calls

System Programs

Operating System Design and Implementation

Operating System Structure

Virtual Machines

Operating System Generation

System Boot

Page 3: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.3/56

ObjectivesObjectives

To describe the services an operating system provides to users, processes, and other systems

To discuss the various ways of structuring an operating system

To explain how operating systems are installed and customized and how they boot

------------------------------------------------------------------

We can view an operating system from several vantage points. One view focuses on the services that the system provides; another, on the interface that it makes available to users and programmers; a third, on its components and their interconnections.

P39

Page 4: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.4/56

Operating System ServicesOperating System Services

One set of operating-system services provides functions that are helpful to the user: User interface - Almost all operating systems have a

user interface (UI)

Varies between Command-Line (CLI), Graphics User Interface (GUI), Batch

Program execution - The system must be able to load a program into memory and to run that program, end execution, either normally or abnormally (indicating error)

I/O operations - A running program may require I/O, which may involve a file or an I/O device.

P40

Page 5: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.5/56

Operating System Services (Cont.)Operating System Services (Cont.)

I/O operations - A running program may require I/O, which may involve a file or an I/O device.

File-system manipulation - The file system is of particular interest. Obviously, programs need to read and write files and directories, create and delete them, search them, list file Information, permission management.

Communications – Processes may exchange information, on the same computer or between computers over a network

Communications may be via shared memory or through message passing (packets moved by the OS)

Page 6: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.6/56

Operating System Services (Cont.)Operating System Services (Cont.)

Error detection – OS needs to be constantly aware of possible errors

May occur in the CPU and memory hardware, in I/O devices, in user program

For each type of error, OS should take the appropriate action to ensure correct and consistent computing

Debugging facilities can greatly enhance the user’s and programmer’s abilities to efficiently use the system

Page 7: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.7/56

Operating System Services (Cont.)Operating System Services (Cont.)

Another set of operating-system functions exists not for helping the user but rather for ensuring the efficient operation of the system itself. Resource allocation - When multiple users or multiple

jobs running concurrently, resources must be allocated to each of them

Accounting - To keep track of which users use how much and what kinds of computer resources

Protection and security - The owners of information stored in a multiuser or networked computer system may want to control use of that information, concurrent processes should not interfere with each other

Page 8: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.8/56

User Operating System InterfaceUser Operating System Interface

There are two fundamental approaches for users to interface with the operating system.

One technique is to provide a command-line interface (CLI) or command interpreter that allows users to directly enter commands that are to be performed by the operating system.

The second approach allows the user to interface with the operating system via a graphical user interface or GUI.

P41

Page 9: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.9/56

User Operating System Interface - CLIUser Operating System Interface - CLI

The main function of the command interpreter is to get and execute the next user-specified command.

In one approach: the command interpreter itself contains the code to execute the command.--- 内部命令

An alternative approach: used by UNIX, among other operating systems, implements most commands through system programs.---外部命令

Page 10: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.10/56

User Operating System Interface - GUIUser Operating System Interface - GUI

User-friendly desktop metaphor interface

Usually mouse, keyboard, and monitor

Icons represent files, programs, actions, etc

Various mouse buttons over objects in the interface cause various actions (provide information, options, execute function, open directory (known as a folder)

Invented at Xerox PARC

Page 11: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.11/56

User Operating System Interface - GUIUser Operating System Interface - GUI

Many systems now include both CLI and GUI interfaces

Microsoft Windows is GUI with CLI “command” shell

Apple Mac OS X as “Aqua” GUI interface with UNIX kernel underneath and shells available

Solaris is CLI with optional GUI interfaces (Java Desktop, KDE)

Page 12: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.12/56

User Operating System InterfaceUser Operating System Interface

The choice of whether to use a command-line or GUI interface is mostly one of personal preference.

The user interface can vary from system to system and even from user to user within a system. It typically is substantially removed from the actual system structure.

The design of a useful and friendly user interface is therefore not a direct function of the operating system.

Page 13: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.13/56

System CallsSystem Calls

Programming interface to the services provided by the OS

Typically written in a high-level language (C or C++) Mostly accessed by programs via a high-level

Application Program Interface (API) rather than direct system call use

Three most common APIs are Win32 API for Windows, POSIX API for POSIX-based systems (including virtually all versions of UNIX, Linux, and Mac OS X), and Java API for the Java virtual machine (JVM)

P43

Page 14: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.14/56

System CallsSystem Calls

Why use APIs rather than system calls?

One benefit of programming according to an API concerns program portability: An application programmer designing a program using an API can expect her program to compile and run on any system that supports the same API

actual system calls can often be more detailed and difficult to work with than the API available to an application programmer.

Page 15: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.15/56

Example of System CallsExample of System Calls System call sequence to copy the contents of one

file to another file

Page 16: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.16/56

Example of Standard APIExample of Standard API

Consider the ReadFile() function in the Win32 API—a function for reading from a file

Page 17: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.17/56

API – System Call – OS RelationshipAPI – System Call – OS Relationship

Page 18: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.18/56

Standard C Library ExampleStandard C Library Example

C program invoking printf() library call, which calls write() system call

Page 19: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.19/56

System Call Parameter PassingSystem Call Parameter Passing

Often, more information is required than simply identity of desired system call Exact type and amount of information vary according

to OS and call Three general methods used to pass parameters to the

OS Simplest: pass the parameters in registers

In some cases, may be more parameters than registers

P47

Page 20: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.20/56

System Call Parameter PassingSystem Call Parameter Passing

Parameters stored in a block, or table, in memory, and address of block passed as a parameter in a register This approach taken by Linux and Solaris

Parameters placed, or pushed, onto the stack by the program and popped off the stack by the operating system

Block and stack methods do not limit the number or length of parameters being passed

Page 21: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.21/56

Parameter Passing via TableParameter Passing via Table

Page 22: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.22/56

Types of System CallsTypes of System Calls

Process control

File management

Device management

Information maintenance

Communications

P47-54

Page 23: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.23/56

System ProgramsSystem Programs

System programs provide a convenient environment for program development and execution. The can be divided into:

File manipulation

Status information

File modification

Programming language support

Program loading and execution

Communications

Application programs

P55

Page 24: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.24/56

System ProgramsSystem Programs

The view of the operating system seen by most users is defined by the application and system programs, rather than by the actual system calls.

Page 25: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.25/56

System ProgramsSystem Programs

Provide a convenient environment for program development and execution

Some of them are simply user interfaces to system calls; others are considerably more complex

File management - Create, delete, copy, rename, print, dump, list, and generally manipulate files and directories

Page 26: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.26/56

System ProgramsSystem Programs

Status information

Some ask the system for info - date, time, amount of available memory, disk space, number of users

Others provide detailed performance, logging, and debugging information

Typically, these programs format and print the output to the terminal or other output devices

Some systems implement a registry - used to store and retrieve configuration information

Page 27: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.27/56

System Programs System Programs

File modification Text editors to create and modify files Special commands to search contents of files

or perform transformations of the text Programming-language support - Compilers,

assemblers, debuggers and interpreters sometimes provided

Program loading and execution- Absolute loaders, re-locatable loaders, linkage editors, and overlay-loaders, debugging systems for higher-level and machine language

Page 28: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.28/56

System Programs System Programs

Communications - Provide the mechanism for creating virtual connections among processes, users, and computer systems Allow users to send messages to one another’s

screens, browse web pages, send electronic-mail messages, log in remotely, transfer files from one machine to another

Page 29: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.29/56

Operating System Design and ImplementationOperating System Design and Implementation

The first problem in designing a system is to define goals and specifications.

At the highest level, the design of the system will be affected by the choice of hardware and the type of system: batch, time shared, single user, multiuser, distributed, real time, or general purpose.

User goals and System goals

User goals – operating system should be convenient to use, easy to learn, reliable, safe, and fast

System goals – operating system should be easy to design, implement, and maintain, as well as flexible, reliable, error free, and efficient

P56

Page 30: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.30/56

Operating System Design and Implementation (Cont.)Operating System Design and Implementation (Cont.)

Important principle to separate

Policy: What will be done? Mechanism: How to do it?

Mechanisms determine how to do something, policies decide what will be done

For example, the timer construct (see Section 1.5.2) is a mechanism fur ensuring CPU protection, but deciding how long the timer is to be set for a particular user is a policy decision.

The separation of policy from mechanism is a very important principle, it allows maximum flexibility if policy decisions are to be changed later

Page 31: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.31/56

Operating-System StructureOperating-System Structure

A system as large and complex as a modern operating system must be engineered carefully if it is to function properly and be modified easily.

A common approach is to partition the task into small components rather than have one monolithic system. Each of these modules should be a well-defined portion of the system, with carefully defined inputs, outputs, and functions.

how these components are interconnected and melded into a kernel? --------Operating system structure

P58

Page 32: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.32/56

Simple Structure Simple Structure

MS-DOS – written to provide the most functionality in the least space

Not divided into modules

Although MS-DOS has some structure, its interfaces and levels of functionality are not well separated

P59

Page 33: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.33/56

MS-DOS Layer StructureMS-DOS Layer Structure

IO.SYS

MSDOS.SYS

COMMAND.COM

Page 34: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.34/56

UNIXUNIX

UNIX – limited by hardware functionality, the original UNIX operating system had limited structuring. The UNIX OS consists of two separable parts

Systems programs

The kernel

Consists of everything below the system-call interface and above the physical hardware

Provides the file system, CPU scheduling, memory management, and other operating-system functions; a large number of functions for one level

P59

Page 35: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.35/56

UNIX System StructureUNIX System Structure

Page 36: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.36/56

Layered ApproachLayered Approach

The operating system is divided into a number of layers (levels), each built on top of lower layers. The bottom layer (layer 0), is the hardware; the highest (layer N) is the user interface.

An operating-system layer is an implementation of an abstract object made up of data and the operations that can manipulate those data.

A typical operating-system layer-say, layer M-consists of data structures and a set of routines that can be invoked by higher-level layers. Layer M, in turn, can invoke operations on lower-level layers.

P59-60

Page 37: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.37/56

Layered Operating SystemLayered Operating System

Page 38: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.38/56

Layered ApproachLayered Approach

The main advantage of the layered approach is simplicity of construction and debugging. Each layer is implemented with only those operations

provided by lower level layers. A layer does not need to know how these operations are implemented; it needs to know only what these operations do. Hence, each layer hides the existence of certain data structures, operations, and hardware from higher-level layers.

Page 39: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.39/56

Layered ApproachLayered Approach

The major difficulty with the layered approach involves appropriately defining the various layers. Because a layer can use only lower-level layers,

careful planning is necessary A final problem with layered implementations is that they

tend to be less efficient than other types. These limitations have caused a small backlash against

layering in recent years. Fewer layers with more functionality are being designed, providing most of the advantages of modularized code while avoiding the difficult problems of layer definition and interaction.

Page 40: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.40/56

Microkernel System Structure Microkernel System Structure

removing all nonessential components from the kernel and implementing them as system and user-level programs.

There is little consensus regarding which services should remain in the kernel and which should be implemented in user space.

Typically, however, micro-kernels provide minimal process and memory management, in addition to a communication facility.

P61-62

Page 41: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.41/56

Microkernel System Structure Microkernel System Structure

The main function of the microkernel is to provide a communication facility between the client program and the various services that are also running in user space.

Communication is provided by message passing

The client program and service never interact directly.

Page 42: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.42/56

Microkernel System Structure Microkernel System Structure

Benefits:

Easier to extend a microkernel

Easier to port the operating system to new architectures

More reliable (less code is running in kernel mode)

More secure

Unfortunately, micro-kernels can suffer from performance decreases due to increased system function overhead.

Page 43: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.43/56

Microkernel System Structure Microkernel System Structure

Consider the history of Windows NT. The first release had a layered microkernel organization. However, this version delivered low performance compared with that of Windows 95. Windows NT 4.0 partially redressed the performance problem by moving layers from user space to kernel space and integrating them more closely. By the time Windows XP was designed, its architecture was more monolithic than microkernel.

Page 44: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.44/56

ModulesModules Most modern operating systems implement kernel

modules

Uses object-oriented approach

Each core component is separate

Each talks to the others over known interfaces

Each is loadable as needed within the kernel

Such a design allows the kernel to provide core services yet also allows certain features to be implemented dynamically.

P62-63

Page 45: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.45/56

ModulesModules The overall result resembles a layered system in that

each kernel section has defined, protected interfaces; but it is more flexible than a layered system in that any module can call any other module.

Furthermore, the approach is like the microkernel approach in that the primary module has only core functions and knowledge of how to load and communicate with other modules; but it is more efficient, because modules do not need to invoke message passing in order to communicate.

Page 46: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.46/56

Solaris Modular ApproachSolaris Modular Approach

Page 47: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.47/56

Virtual MachinesVirtual Machines

The fundamental idea behind a virtual machine is to abstract the hardware of a single computer (the CPU, memory, disk drives, network interface cards, and so forth) into several different execution environments, thereby creating the illusion that each separate execution environment is running its own private computer.

The virtual-machine approach does not provide any such additional functionality but rather provides an interface that is identical to the underlying bare hardware.

P64

Page 48: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.48/56

Virtual MachinesVirtual Machines

There are several reasons for creating a virtual machine, all of which are fundamentally related to being able to share the same hardware yet run several different execution environments (that is, different operating systems) concurrently.

Page 49: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.49/56

Virtual Machines Virtual Machines

(a) Non virtual machine (b) virtual machine

Non-virtual Machine Virtual Machine

Page 50: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.50/56

Virtual Machines Virtual Machines

By using CPU scheduling and virtual-memory techniques, an operating system can create the illusion that a process has its own processor with its own (virtual) memory.

The virtual-machine software can run in kernel mode, since it is the operating system. The virtual machine itself can execute in only user mode. Just as the physical machine has two modes, however, so must the virtual machine. Consequently, we must have a virtual user mode and a virtual kernel mode, both of which run in a physical user mode.

Page 51: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.51/56

Virtual MachinesVirtual Machines

The virtual-machine concept provides complete protection of system resources since each virtual machine is isolated from all other virtual machines. This isolation, however, permits no direct sharing of resources.

A virtual-machine system is a perfect vehicle for operating-systems research and development. System development is done on the virtual machine, instead of on a physical machine and so does not disrupt normal system operation.

The virtual machine concept is difficult to implement due to the effort required to provide an exact duplicate to the underlying machine

Page 52: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.52/56

VMware ArchitectureVMware Architecture

Page 53: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.53/56

The Java Virtual MachineThe Java Virtual Machine

Page 54: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.54/56

Operating System GenerationOperating System Generation

Operating systems are designed to run on any of a class of machines; the system must be configured for each specific computer site

SYSGEN program obtains information concerning the specific configuration of the hardware system

Booting – starting a computer by loading the kernel

Bootstrap program – code stored in ROM that is able to locate the kernel, load it into memory, and start its execution

Page 55: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

2.55/56

System BootSystem Boot

Operating system must be made available to hardware so hardware can start it

Small piece of code – bootstrap loader, locates the kernel, loads it into memory, and starts it

Sometimes two-step process where boot block at fixed location loads bootstrap loader

When power initialized on system, execution starts at a fixed memory location

Firmware used to hold initial boot code

Page 56: Chapter 2: Operating-System Structures. 2.2/56 Chapter 2: Operating-System Structures Operating System Services User Operating System Interface System

HomeworkHomework :: 11、、 22、、 77、、 88、、 1111 、、 1212、、 1414

End of Chapter 2End of Chapter 2