2800 Lecture2 Os Structure

Chapter 2: Operating-System Structures
Operating System Concepts with Java – 8th Edition 2.1 Silberschatz, Galvin and Gagne ©2009
Chapter 2: Operating-System Structures
n Operating System Services

n User Operating System Interface
n System Calls
n Types of System Calls
n System Programs
n Operating System Design and Implementation
n Operating System Structure
n Virtual Machines
Objectives
n To describe the services an operating system

provides to users, processes, and other
systems
n To discuss the various ways of structuring an
operating system
2.1 Operating System Services
n One set of operating-system services provides functions

that are helpful to the user:
l User interface - Almost all operating systems have a
user interface (UI)
4Varies between Command-Line (CLI), Graphics
User Interface (GUI), Batch
l 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)
A View of Operating System Services
2.1 Operating System Services (Cont)
n One set of operating-system services provides functions that
are helpful to the user (Cont):
l I/O operations - A running program may require I/O, which
may involve a file or an I/O device
l 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.
l Communications – Processes may exchange information,
on the same computer or between computers over a
network
4 Communications may be via shared memory or through
message passing (packets moved by the OS)
n Another set of OS functions exists for ensuring the efficient
operation of the system itself via resource sharing
l Error detection – OS needs to be constantly aware of
possible errors
4May occur in the CPU and memory hardware, in I/O
devices, in user program
4For each type of error, OS should take the appropriate
action to ensure correct and consistent computing
4Debugging facilities can greatly enhance the user’s
and programmer’s abilities to efficiently use the
system
n Another set of OS functions exists for ensuring the
efficient operation of the system itself via resource
sharing
l Resource allocation - When multiple users or
multiple jobs running concurrently, resources must be
allocated to each of them
4Many types of resources - Some (such as CPU
cycles, main memory, and file storage) may have
special allocation code, others (such as I/O devices)
may have general request and release code
l Accounting - To keep track of which users use how
much and what kinds of computer resources
n Another set of OS functions exists for ensuring the efficient
operation of the system itself via resource sharing
l 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
4Protection involves ensuring that all access to system
resources is controlled
4Security of the system from outsiders requires user
authentication, extends to defending external I/O
devices from invalid access attempts
4If a system is to be protected and secure, precautions
must be instituted throughout it. A chain is only as
strong as its weakest link.
2.2 User Operating System Interface
n Command Line Interface (CLI) or command interpreter allows

direct command entry
l Sometimes implemented in kernel, sometimes by systems
program
l Sometimes multiple flavors implemented – shells
l Primarily fetches a command from user and executes it
n User-friendly desktop metaphor interface
l Usually mouse, keyboard, and monitor
l Icons represent files, programs, actions, etc
l Various mouse buttons over objects in the interface cause
various actions (provide information, options, execute function,
open directory (known as a folder)
2.2 User Operating System Interface
n Many systems now include both CLI and GUI

interfaces
l MicrosoftWindows is GUI with CLI
“command” shell
l Apple Mac OS X as “Aqua” GUI interface
with UNIX kernel underneath and shells
available
l Solaris is CLI with optional GUI interfaces
(Java Desktop, KDE)
Bourne Shell Command Interpreter
The Mac OS X GUI
2.3 System Calls
n Programming interface to the services provided by the OS

n Typically written in a high-level language (C or C++)
n Mostly accessed by programs via a high-level Application
Program Interface (API) rather than direct system call use
n 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)
n Why use APIs rather than system calls?
(Note that the system-call names used throughout this text are
generic)
Example of System Calls
n System call sequence to copy the contents

of one file to another file
Example of Standard API
n Consider the ReadFile() function in the
n Win32 API—a function for reading from a file
n A description of the parameters passed to ReadFile()

l HANDLE file—the file to be read
l LPVOID buffer—a buffer where the data will be read into and written from
l DWORD bytesToRead—the number of bytes to be read into the buffer
l LPDWORD bytesRead—the number of bytes read during the last read
l LPOVERLAPPED ovl—indicates if overlapped I/O is being used
System Call Implementation
n Typically, a number associated with each system call

l System-call interface maintains a table indexed according to
these numbers
n The system call interface invokes intended system call in OS
kernel and returns status of the system call and any return
values
n The caller need know nothing about how the system call is
implemented
l Just needs to obey API and understand what OS will do as a
result call
l Most details of OS interface hidden from programmer by
API
API – System Call – OS Relationship
Standard C Library Example
n C program invoking printf() library call, which calls
write() system call
System Call Parameter Passing
n Often, more information is required than simply identity of desired
system call
Exact type and amount of information vary according to OS and
l
call
n Three general methods used to pass parameters to the OS
l Simplest: pass the parameters in registers
4 In some cases, may be more parameters than registers
l Parameters stored in a block, or table, in memory, and address of
block passed as a parameter in a register
4 This
approach taken by Linux and Solaris
l Parameters placed, or pushed, onto the stack by the program and
popped off the stack by the operating system
l Block and stack methods do not limit the number or length of
parameters being passed
Parameter Passing via Table
2.4 Types of System Calls
n Process control
n File management
n Device management
n Information maintenance
n Communications
n Protection
Examples of Windows and Unix System Calls
MS-DOS execution
(a) At system startup (b) running a program
FreeBSD Running Multiple Programs
• Example of multi-tasking system.

• Command interpreter may continue
to running while another program is
executed.
• fork(): start a new process
• exec(): load a selected program to
memory
2.5 System Programs
n System programs (system utilities) provide a convenient
environment for program development and execution. The can
be divided into:
l File manipulation
l Status information
l File modification
l Programming language support
l Program loading and execution
l Communications
l Application programs
n Most users’ view of the operation system is defined by system
programs, not the actual system calls
System Programs (cont’d)
n File management - Create, delete, copy,

rename, print, dump, list, and generally
manipulate files and directories
n Status information
l Some ask the system for info - date, time, amount of
available memory, disk space, number of users
l Others provide detailed performance, logging, and
debugging information
l Typically, these programs format and print the output to
the terminal or other output devices
l Some systems implement a registry - used to store and
retrieve configuration information
n File modification
l Text
editors to create and modify files
l Special commands to search contents of
files or perform transformations of the text
n Programming-language support - Compilers,
assemblers, debuggers and interpreters
sometimes provided
n Program loading and execution- Absolute loaders,
relocatable loaders, linkage editors, and overlay-
loaders, debugging systems for higher-level and
machine language
n Communications - Provide the mechanism for
creating virtual connections among processes, users,
and computer systems
l 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
2.6 Operating System Design and Implementation
n Design and Implementation of OS is not “solvable”, but some

approaches have proven successful
n Internal structure of different Operating Systems can vary
widely
n Start by defining goals and specifications
n Affected by choice of hardware, type of system
n User goals and System goals
l User goals – operating system should be convenient to
use, easy to learn, reliable, safe, and fast
l System goals – operating system should be easy to
design, implement, and maintain, as well as flexible,
reliable, error-free, and efficient
2.6 Operating System Design and Implementation (Cont)
n Important principle to separate

Policy: What will be done?
Mechanism: How to do it?
n Mechanisms determine how to do something,
policies decide what will be done
l The separation of policy from mechanism is a
very important principle, it allows maximum
flexibility if policy decisions are to be
changed later
Simple Structure
n MS-DOS – written to provide the most

functionality in the least space
l Not divided into modules
l Although MS-DOS has some structure, its
interfaces and levels of functionality are
not well separated
MS-DOS Layer Structure
Layered Approach
n 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.
n With modularity, layers are selected such that
each uses functions (operations) and services
of only lower-level layers
Traditional UNIX System Structure
UNIX
n UNIX – limited by hardware functionality, the original

UNIX operating system had limited structuring. The UNIX
OS consists of two separable parts
l Systems programs
l The kernel
4 Consists of everything below the system-call
interface and above the physical hardware
4 Provides the file system, CPU scheduling, memory
management, and other operating-system functions;
a large number of functions for one level
Layered Operating System
Microkernel System Structure
n Moves as much from the kernel into “user” space

n Communication takes place between user modules using
message passing
n Benefits:
l Easier to extend a microkernel
l Easier to port the operating system to new architectures
l More reliable (less code is running in kernel mode)
l More secure
n Detriments:
l Performance overhead of user space to kernel space
communication
Mac OS X Structure
• Hybrid of layered system
and microkernel.
• Mach provides memory
management and
interprocess
communication
• BSC provide cli,
networking, file system
and POSIX APIs.
Modules
n Most modern operating systems implement

kernel modules
l Uses object-oriented approach
l Each core component is separate
l Each talks to the others over known interfaces
l Each is loadable as needed within the kernel
n Overall, similar to layers but with more flexible
Solaris Modular Approach
Virtual Machines
n A virtual machine takes the layered approach to its

logical conclusion. It treats hardware and the
operating system kernel as though they were all
hardware
n A virtual machine provides an interface identical to
the underlying bare hardware
n The operating system host creates the illusion that a
process has its own processor and (virtual memory)
n Each guest provided with a (virtual) copy of
underlying computer
Virtual Machines History and Benefits
n First appeared commercially in IBM mainframes in 1972
n Fundamentally, multiple execution environments (different operating
systems) can share the same hardware
n Protect from each other
n Some sharing of file can be permitted, controlled
n Commutate with each other, other physical systems via networking
n Useful for development, testing
n Consolidation of many low-resource use systems onto fewer busier
systems
n “Open Virtual Machine Format”, standard format of virtual machines,
allows a VM to run within many different virtual machine (host)
platforms
Virtual Machines (Cont)
Non-virtual Machine Virtual Machine
(a) Nonvirtual machine (b) virtual machine
Para-virtualization
n Presents guest with system similar but not

identical to hardware
n Guest must be modified to run on paravirtualized
hardwareF
n Guest can be an OS, or in the case of Solaris 10
applications running in containers
Solaris 10 with Two Containers
VMware Architecture
Java
n Java consists of
1. Programming language specification
2. Application programming interface (API)
3. Virtual machine specification
The Java Virtual Machine
The Java Virtual Machine
Java portability across platforms.
The Java Development Kit
Java Operating Systems
The JX operating system
End of Chapter 2

2800 Lecture2 Os Structure

Uploaded by

Copyright:

Available Formats

2800 Lecture2 Os Structure

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2800 Lecture2 Os Structure

Uploaded by

Copyright:

Available Formats

Chapter 2: Operating-System Structures

n Operating System Services

n To describe the services an operating system

n One set of operating-system services provides functions

n Command Line Interface (CLI) or command interpreter allows

n Many systems now include both CLI and GUI

n Programming interface to the services provided by the OS

n System call sequence to copy the contents

n A description of the parameters passed to ReadFile()

n Typically, a number associated with each system call

(a) At system startup (b) running a program

• Example of multi-tasking system.

n File management - Create, delete, copy,

n Design and Implementation of OS is not “solvable”, but some

n Important principle to separate

n MS-DOS – written to provide the most

n The operating system is divided into a number

n UNIX – limited by hardware functionality, the original

n Moves as much from the kernel into “user” space

n Most modern operating systems implement

n A virtual machine takes the layered approach to its

Non-virtual Machine Virtual Machine

(a) Nonvirtual machine (b) virtual machine

n Presents guest with system similar but not

The JX operating system

You might also like