內容文本文稿ch

1、Chapter 2: Operating-System StructuresChapter 2: Operating-System StructuresOperating System ServicesUser Operating System InterfaceSystem CallsTypes of System CallsSystem ProgramsOperating System Design and ImplementationOperating System StructureVirtual MachinesOperating System GenerationSystem Bo

2、otObjectivesTo describe the services an operating system provides to users, processes, and other systemsTo discuss the various ways of structuring an operating systemTo explain how operating systems are installed and customized and how they bootOperating System ServicesOne set of operating-system se

3、rvices 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), BatchProgram execution - The system must be able to load a program into memory and to run that program, end

4、 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. File-system manipulation - The file system is of particular interest. Obviously, programs need to read and write files and directories, create an

5、d delete them, search them, list file Information, permission management.Operating System Services (Cont.)One set of operating-system services provides functions that are helpful to the user (Cont):Communications Processes may exchange information, on the same computer or between computers over a ne

6、tworkCommunications may be via shared memory or through message passing (packets moved by the OS)Error detection OS needs to be constantly aware of possible errorsMay occur in the CPU and memory hardware, in I/O devices, in user programFor each type of error, OS should take the appropriate action to

7、 ensure correct and consistent computingDebugging facilities can greatly enhance the users and programmers abilities to efficiently use the systemOperating System Services (Cont.)Another set of OS functions exists for ensuring the efficient operation of the system itself via resource sharingResource

8、 allocation - When multiple users or multiple jobs running concurrently, resources must be allocated to each of themMany types of resources - Some (such as CPU cycles,mainmemory, and file storage) may have special allocation code, others (such as I/O devices) may have general request and release cod

9、e. Accounting - To keep track of which users use how much and what kinds of computer resourcesProtection 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 otherP

10、rotection involves ensuring that all access to system resources is controlledSecurity of the system from outsiders requires user authentication, extends to defending external I/O devices from invalid access attemptsIf a system is to be protected and secure, precautions must be instituted throughout

11、it. A chain is only as strong as its weakest link.User Operating System Interface - CLICLI allows direct command entrySometimes implemented in kernel, sometimes by systems programSometimes multiple flavors implemented shellsPrimarily fetches a command from user and executes itSometimes commands buil

12、t-in, sometimes just names of programsIf the latter, adding new features doesnt require shell modificationUser Operating System Interface - GUIUser-friendly desktop metaphor interfaceUsually mouse, keyboard, and monitorIcons represent files, programs, actions, etcVarious mouse buttons over objects i

13、n the interface cause various actions (provide information, options, execute function, open directory (known as a folder)Invented at Xerox PARCMany systems now include both CLI and GUI interfacesMicrosoft Windows is GUI with CLI “command” shellApple Mac OS X as “Aqua” GUI interface with UNIX kernel

14、underneath and shells availableSolaris is CLI with optional GUI interfaces (Java Desktop, KDE)System CallsProgramming interface to the services provided by the OSTypically written in a high-level language (C or C+)Mostly accessed by programs via a high-level Application Program Interface (API) rathe

15、r than direct system call useThree 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)Why use APIs rather than system calls?(Note that the system-call names used

16、 throughout this text are generic)Example of System CallsSystem call sequence to copy the contents of one file to another fileExample of Standard APIConsider the ReadFile() function in theWin32 APIa function for reading from a fileA description of the parameters passed to ReadFile()HANDLE filethe fi

17、le to be readLPVOID buffera buffer where the data will be read into and written fromDWORD bytesToReadthe number of bytes to be read into the bufferLPDWORD bytesReadthe number of bytes read during the last readLPOVERLAPPED ovlindicates if overlapped I/O is being usedSystem Call ImplementationTypicall

18、y, a number associated with each system callSystem-call interface maintains a table indexed according to these numbersThe system call interface invokes intended system call in OS kernel and returns status of the system call and any return valuesThe caller need know nothing about how the system call

19、is implementedJust needs to obey API and understand what OS will do as a result callMost details of OS interface hidden from programmer by API Managed by run-time support library (set of functions built into libraries included with compiler)API System Call OS RelationshipStandard C Library ExampleC

20、program invoking printf() library call, which calls write() system callSystem Call Parameter PassingOften, more information is required than simply identity of desired system callExact type and amount of information vary according to OS and callThree general methods used to pass parameters to the OS

21、Simplest: pass the parameters in registers In some cases, may be more parameters than registersParameters 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 SolarisParameters placed, or pushed, onto the stack by the progr

22、am and popped off the stack by the operating systemBlock and stack methods do not limit the number or length of parameters being passedParameter Passing via TableTypes of System CallsProcess controlFile managementDevice managementInformation maintenanceCommunicationsMS-DOS execution(a) At system sta

23、rtup (b) running a programFreeBSD Running Multiple ProgramsSystem ProgramsSystem programs provide a convenient environment for program development and execution. The can be divided into:File manipulation Status informationFile modificationProgramming language supportProgram loading and executionComm

24、unicationsApplication programsMost users view of the operation system is defined by system programs, not the actual system callsSolaris 10 dtrace Following System CallSystem ProgramsProvide a convenient environment for program development and executionSome of them are simply user interfaces to syste

25、m calls; others are considerably more complexFile management - Create, delete, copy, rename, print, dump, list, and generally manipulate files and directoriesStatus informationSome ask the system for info - date, time, amount of available memory, disk space, number of usersOthers provide detailed pe

26、rformance, logging, and debugging informationTypically, these programs format and print the output to the terminal or other output devicesSome systems implement a registry - used to store and retrieve configuration informationSystem Programs (contd)File modificationText editors to create and modify

27、filesSpecial commands to search contents of files or perform transformations of the textProgramming-language support - Compilers, assemblers, debuggers and interpreters sometimes providedProgram loading and execution- Absolute loaders, relocatable loaders, linkage editors, and overlay-loaders, debug

28、ging systems for higher-level and machine languageCommunications - Provide the mechanism for creating virtual connections among processes, users, and computer systemsAllow users to send messages to one anothers screens, browse web pages, send electronic-mail messages, log in remotely, transfer files

29、 from one machine to anotherOperating System Design and ImplementationDesign and Implementation of OS not “solvable”, but some approaches have proven successfulInternal structure of different Operating Systems can vary widelyStart by defining goals and specifications Affected by choice of hardware,

30、type of systemUser goals and System goalsUser goals operating system should be convenient to use, easy to learn, reliable, safe, and fastSystem goals operating system should be easy to design, implement, and maintain, as well as flexible, reliable, error-free, and efficientOperating System Design an

31、d Implementation (Cont.)Important principle to separatePolicy: What will be done? Mechanism: How to do it?Mechanisms determine how to do something, policies decide what will be doneThe separation of policy from mechanism is a very important principle, it allows maximum flexibility if policy decision

32、s are to be changed laterSimple Structure MS-DOS written to provide the most functionality in the least spaceNot divided into modulesAlthough MS-DOS has some structure, its interfaces and levels of functionality are not well separatedMS-DOS Layer StructureLayered ApproachThe operating system is divi

33、ded 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.With modularity, layers are selected such that each uses functions (operations) and services of only lower-level layersLayered Operating S

34、ystemUNIXUNIX limited by hardware functionality, the original UNIX operating system had limited structuring. The UNIX OS consists of two separable partsSystems programsThe kernelConsists of everything below the system-call interface and above the physical hardwareProvides the file system, CPU schedu

35、ling, memory management, and other operating-system functions; a large number of functions for one levelUNIX System StructureMicrokernel System Structure Moves as much from the kernel into “user” spaceCommunication takes place between user modules using message passingBenefits:Easier to extend a mic

36、rokernelEasier to port the operating system to new architecturesMore reliable (less code is running in kernel mode)More secureDetriments:Performance overhead of user space to kernel space communicationMac OS X StructureModulesMost modern operating systems implement kernel modulesUses object-oriented

37、 approachEach core component is separateEach talks to the others over known interfacesEach is loadable as needed within the kernelOverall, similar to layers but with more flexibleSolaris Modular ApproachVirtual MachinesA virtual machine takes the layered approach to its logical conclusion. It treats

38、 hardware and the operating system kernel as though they were all hardwareA virtual machine provides an interface identical to the underlying bare hardwareThe operating system creates the illusion of multiple processes, each executing on its own processor with its own (virtual) memoryVirtual Machine

39、s (Cont.)The resources of the physical computer are shared to create the virtual machinesCPU scheduling can create the appearance that users have their own processorSpooling and a file system can provide virtual card readers and virtual line printersA normal user time-sharing terminal serves as the virtual machine operators consoleVirtual Machines (Cont.) (a) Nonvirtual machine (b) virtual machineNon-virtual MachineVirtual MachineVirtual Machines (Cont.)The virtual-machine concept provides complete protection of system resources since each virtual machine