Please enable JavaScript.
Coggle requires JavaScript to display documents.
Operating Systems (OS), ALEND HARRICK LUKAS 73318 - Coggle Diagram
Operating Systems (OS)
OS Overview
-
-
OS as a resource manager
OS direct the processor in the use of other system resources and in the timing of its execution of other programs
OS hands over control for the processor to do work and the resumes control long enough to prepare the processor to do next work
OS is the master program that has control over smaller user programs and share computer resources with all programs
-
OS Component
5 Major Components
Device Manage
Monitors every device, channel and control unit
Choose the most efficient way to allocate all of the system's devices, printers, ports, disk drives, etc. based on the scheduling policy
Allocating each resource, starting its operation and finally deallocating the device making it available to the next process or job
File Manager
Data files, program files, compilers, application
-
-
-
-
-
Processor Manager
-
Monitors whether the CPU is executing a process or waiting for a
READ/WRITE command to finish execution
-
Like a traffic controller, the CPU handles the processes’ transition from one
state of execution to another
-
-
Memory Manager
-
-
-
-
-
In multiuser environment, sets up table to track memory usage
-
OS Types
-
-
-
Everyday OS VS Server OS
Everday OS
-
-
Runs program such as MS Office, computer games, web browsing, checking email etc.
-
-
-
Cooperation
- If the program is in storage, the File Manager (FM) must calculate its exact location on the disk and pass this information to the DM, which retrieves the program and sends to Memory Manager (MM)
- The MM finds a space for the program and records its exact location in memory. Once in memory, the MM must track the program's location and progress as it is being executed by the PM
- When the PM receives the command, it checks whether the program must be retrieved from storage or is already in memory and the notifies the appropriate manager
- When the program has finished executing, it must send a finished message to the PM to that PM can assign the processor to the next program in line.
- The PM sends an acknowledgement message to be displayed on the screen so the user knows that the command has been sent
- Lastly, the PM must forward the finished to the DM so that it can notify the user and refresh the screen
- The Device Manager (DM) receives the electrical impulses from the keyboard/mouse, forms the command and sends the command to the UI where the Process Manager (PM) validates the command
-