Chapter 3 Operating System Structures

Get Started. It's Free
or sign up with your email address
Rocket clouds
Chapter 3 Operating System Structures by Mind Map: Chapter 3  Operating System Structures

1. Operating System Services

1.1. User Interface

1.1.1. Almost all operating systems have a user interface (UI).

1.2. Program Execution

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

1.3. I/O

1.3.1. Since user programs cannot execute I/O operations directly, the operating system must provide some means to perform I/O.

1.4. File-system Manipulation

1.4.1. Program capabilities to read and write files and directories, create and delete them, search them, list file information, permission management.

1.5. Communication

1.5.1. Processes may exchange information, on the same computer or between computers over a network.

1.6. Error detection

1.6.1. Ensure correct computing by detecting errors in the CPU and memory hardware, in I/O devices, or in user programs.

2. Additional Operating System Function

2.1. Protection and Security

2.1.1. 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.

3. System Call

3.1. 1. System calls provide the interface between a running program and the operating system.

3.1.1. Generally available as assembly-language instructions

3.1.2. Languages defined to replace assembly language for systems programming allow system calls to be made directly (e.g., C, C++).

3.2. 2. Three general methods are used to pass parameters between a running program and the operating system

3.2.1. Pass the parameters in registers

3.2.2. Parameters stored in a block, or table, in memory, and address of block passed as a parameter in a register.

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

3.3. 3. Types of System Calls

3.3.1. Process control

3.3.2. File management

3.3.3. Device management

3.3.4. Information maintenance

3.3.5. Communications

3.3.6. Protection

4. Communication Models

4.1. Communication may take place using either message passing or shared memory.

5. Layered Approach

5.1. In layered 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.

5.2. With modularity, layers are selected such that each uses functions (operations) and services of only lower-level layers.

5.3. Advantage

5.3.1. Simplicity of construction and debugging

5.4. Disadvantages

5.4.1. The careful definition and interaction of the layers

5.4.2. Less efficient

6. Benefits of a Microkernel Organization

6.1. Extensibility

6.1.1. Allows the addition of new services

6.2. Flexibility

6.2.1. New features added

6.2.2. Existing features can be subtracted

6.3. Reliability

6.3.1. Modular design

6.3.2. Small microkernel can be rigorously tested

6.4. Portability

6.4.1. Changes needed to port the system to a new processor is changed in the microkernel - not in the other services

7. Operating System Design

7.1. Design and Implementation of OS not “solvable”, but some approaches have proven successful.

7.2. Start by defining goals and specifications

7.3. 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.

8. Operating System Design Goals

8.1. User goals

8.1.1. Operating system should be convenient to use, easy to learn, reliable, safe, and fast.

8.2. System goals

8.2.1. Operating system should be easy to design, implement, and maintain, as well as flexible, reliable, error-free, and efficient.