OS ORGANIZATION Basic OS Responsibilities Create an abstract

OS ORGANIZATION

Basic OS Responsibilities Create an abstract machine environment A nicer environment than bare hardware Consists of multiple, autonomous abstract components Components may be in use concurrently Coordinate the use of the components Resource manager Manage according to the policies of the machine’s administrator 2

Basic OS Functions Exact set of functions required depends on engineering and marketing choices but each function falls in one of these categories: Device management Process, thread, and resource management Memory management File management 3

Basic OS Organization File Manager Process, Thread & Resource Manager Processor(s) Memory Manager Device Manager Main Memory Devices 4

Device Management OS uses policies chosen by designer or system administrator to manage Allocation Isolation Sharing Device manager in two parts Device independent – provides unified interface Device dependent – device driver: handles those aspects unique to a device 5

Device Management – cont. Device-Independent Part Device-Dependent Part Device-Dependent Part … Device 6

Device Management – cont. Application Process System Interface File Manager Device-Independent Hardware Interface Device-Dependent Command Status Data Device Controller 7

Device Management – cont. read(device, …); 1 9 8 b Data System Interface Device Status Table read driver 2 4 7 Device Handler write driver 6 Interrupt Handler 3 8 a 5 Hardware Interface Command Status Data Device Controller 8

Device Management – cont. 9

Life Cycle of an I/O Request 10

Process Management Process Mgr Deadlock Scheduler Protection Process Description Synchronization Resource Manager CPU Other H/W 11

Process, Thread, and Resource Management Thread Abstraction Process Abstraction Generic Resource Manager Multiprogramming Other Primary Memory … Abstract Resources Processor 12

Memory Management Isolation & Sharing Process Manager Block Allocation Primary Memory Virtual Memory Storage Devices 13

Memory Management – cont. 14

Memory Management – cont. 15

Memory Management – cont. 16

File System Management 17

Basic OS Functions Process/Thread Admin Scheduler Virtual Memory File Management Synchronization Device Management IPC Deadlock Management Interrupt Handler Protection Mechanisms Resource Management Memory Allocation 18

OS Design Application Software Other System Software Other OS Functions Kernel Functions Nucleus Functions Skeletal Nucleus (a) Monolithic (b) Modular (c) Extensible (d) Layered (microkernel) 19

Implementation Issues Two recurring issues in design Performance Exclusive use of resources Three basic implementation mechanisms Processor modes Kernels Method of invoking system service 20

Performance Must be as efficient as possible in use of resources (especially processor and memory) Every design issue MUST be evaluated wrt its contribution to functionality of system AND its impact on performance Seek to minimize “overhead” of the system wrt the applications running on the system Increased hardware performance does allow added functionality in spite of inefficiency 21

Typical Computer at 1980 and 2000 22

Exclusive Use of Resources Multiprogramming resource sharing Therefore, need software-controlled resource isolation Security policy: Sharing strategy chosen by computer’s owner Protection mechanism: Tool to implement a family of security policies 23

Exclusive Use of Resources – cont Security depends on correct operation of software trusted vs. untrusted software Need to insure that untrusted software cannot change trusted software Can limit the function of the OS Guiding a manned spaceship Managing a nuclear reactor 24

Processor Modes Mode bit: Supervisor or User mode Some processors may have more than one mode Supervisor mode (privileged, protected) Can execute all machine instructions Can reference all memory locations User mode Can only execute a subset of instructions Can only reference a subset of memory locations 25

Processor Modes – cont Ensures properation of a computer system Protect the operating system and all other programs and their data from any malfunctioning program Protection is needed for any shared resource Trusted OS software runs in supervisor mode All other software runs in user mode 26

Processor Modes – cont Supervisor mode all instructions are legal all addresses are absolute physical addresses (base and bound are not used) User mode instructions that modify control registers are illegal all addresses must be less than bound and have base added to them 27

Privileged Instructions that can only be executed in the supervisor mode are called supervisor, privileged, or protected instructions I/O instructions are privileged instructions A user program in user mode cannot perform its own I/O Instruction to change the mode is a privileged instruction Instruction to set the halt flag is a privileged instruction 28

Exclusive Access to a Resource Processor Process A Process B Supervisor Program A’s Protected Object When A is using processor, register points to its object When B is using processor, register does not point to A’s object 29

Kernels Critical parts of OS that run in supervisor mode Have access to other parts of the kernel Trusted software Extensions to the OS execute in user mode The trap instruction is used to switch from user to supervisor mode, entering the OS 30

Trap Instruction Mode S Branch Table 1 2 trap 3 Trusted Code User Supervisor 31

Trap Instruction … fork(); … fork() { … trap N_SYS_FORK() … } Trap Table – cont. Kernel sys_fork() { /* system function */ … return; } 32

Requesting Services from O. S. Two techniques call Message passing call(…); System trap return; 33

How to Make a System Call For the system through a trap instruction which causes an interrupt Hardware saves PC and current status information Hardware changes mode to system mode Hardware loads PC from system call interrupt vector location. Execute the system call interrupt handler return from the handler, restores PC and other saved status information User process continues. 34

System Call Flow of Control … fork(); … fork() { … trap N_SYS_FORK() … } Trap Table Kernel sys_fork() { /* system function */ … return; } 35

How to Make a System Call – cont. Parameter passing Through registers System call number passed through register Parameters are passed through registers Returned value is also passed through a register to C/C++ Through a table in memory Pass the address of the table in a register Through the stack Push the parameters on the stack by the user program Pop the parameters off the stack by the O. S. 36

A Thread Performing a System Call User Space Kernel Space Thread fork(); sys_fork() { } 37

Requesting Services Two techniques call Message passing – cont. send(…, A, …); receive(…, B, …); System send/receive(…A, …); … send(…, B, …); 38

Basic OS Organization File Manager Process, Thread & Resource Manager Processor(s) Memory Manager Device Manager Main Memory Devices 39

Operating System Examples UNIX MACH MS-DOS Windows NT OS/2 Mac. OS 40

UNIX One of the most popular operating systems First version released in 1969 By Ken Thompson & Dennis Ritchie at Bell Labs ACM Turing Award – 1983 National Medal of Technology – 1999 Japan Prize for Information and Communications – 2011 Widely used in universities and research organizations Time-sharing system Supports multiple processes Disk files and I/O devices are treated similarly 41

History of UNIX Versions 42

Advantages of UNIX Written in a high-level language. Distributed in source form. Provided powerful operating-system primitives on an inexpensive platform. Small size, modular, clean design. 43

UNIX Design Principles Designed to be a time-sharing system Has a simple standard user interface that can be replaced. File system with multilevel tree-structured directories. Files are supported by the kernel as unstructured sequences of bytes. Supports multiple processes; a process can easily create new processes. High priority given to making system interactive, and providing facilities for program development. 44

UNIX System Structure Interactive User Device Driver … Device Driver Interface Libraries Application Commands … Programs OS System Call Interface Trap Table Monolithic Kernel Module • Process Management • Memory Management • File Management • Device Mgmt Infrastructure 45

Current Status UNIX is copyrighted – now supported by SCO long litigious story there! Open source variations freebsd www. freebsd. org/availability. html Linux many distributions 46

Windows NT 32 -bit preemptive multitasking operating system for modern microprocessors. Key goals for the system: portability security POSIX compliance multiprocessor support extensibility international support compatibility with MS-DOS and MS-Windows applications. Uses a micro-kernel architecture. Available in two versions, Windows NT Workstation and Windows NT Server. In 1996, more NT server licenses were sold than UNIX licenses 47

Windows NT Organization T Process T T Libraries Subsystem User Process T T Process Management Memory Management File Management Subsystem Device Mgmt Infrastructure NT Executive NT Kernel Hardware Abstraction Layer Processor(s) Process Main Memory I/O Subsystem Devices 48

History of Windows NT In 1988, Microsoft decided to develop a “new technology” (NT) portable operating system that supported both the OS/2 and POSIX APIs. Originally, NT was supposed to use the OS/2 API as its native environment but during development NT was changed to use the Win 32 API, reflecting the popularity of Windows 3. 0. 49

Windows NT Design Principles Extensibility — layered architecture. NT executive, which runs in protected mode, provides the basic system services. On top of the executive, several server subsystems operate in user mode. Modular structure allows additional environmental subsystems to be added without affecting the executive. 50

Window NT Design Principles Cont. - Portability — NT can be moved from one hardware architecture to another with relatively few changes. Written in C and C++. Processor-dependent code is isolated in a dynamic link library (DLL) called the “hardware abstraction layer” (HAL). Reliability — NT uses hardware protection for virtual memory, and software protection mechanisms for operating system resources. 51

Window NT Design Principles Cont. - Compatibility — applications that follow the IEEE 1003. 1 (POSIX) standard can be complied to run on NT without changing the source code. Performance — NT subsystems can communicate with one another via highperformance message passing. Preemption of low priority threads enables the system to respond quickly to external events. Designed for symmetrical multiprocessing. International support — supports different locales via the national language support (NLS) API. 52

Windows NT Architecture Layered system of modules. Protected mode — HAL, kernel, executive. User mode — collection of subsystems Environmental subsystems emulate different operating systems. Protection subsystems provide security functions. 53