TIME SHARED OS/MULTITASKING OS
• Logical extension of multiprogramming.
• Multiple and interactive users/jobs share the process time.
• Users simultaneously access the system through terminals.
• Each user/job has either burst time or quantum of computation
time.
• On each clock interrupt OS regain control & assign processor to
another user/job.
• Major Problems:
1. Denial of Service.
2. Data Integrity.
3. Privacy Problem.
MULTIPROGRAMMING OS TIME SHARING OS
1. Switching between processes 1. Multiple users / processes
interact
2. Processor time shared with 2. Processor time shared by
multiple processes multiple users.
3. No fixed time slice 3. Has fixed time slice.
4. Non pre-emption mode 4. Pre-emptive / non pre-emptive
execution mode of execution.
5. Minimises response time 5. Maximises processor use
PARALLEL /MULTIPROCESSOR SYSTEM or
TIGHTELY COUPLED SYSTEM
Total time 1 minute
1 min
1 min
1 min
5 min processing time 1 min
1 min
3 advantages:
1. Increased throughput:
Increased processor=>work done increases=>execution time reduced.
2. Economy of sale: Sharing of resources.
3. Increased Reliability: Failure of one processor doesn’t halt the system but only slows
down.
Graceful Degradation: Continue provide service proportional to the level of surviving
hardware.
Fault Tolerant: A process that enables the OS to respond to any h/w or s/w failure.
Asymmetric
(Master Slave relation)
Parallel OS multiprocessing
Symmetric All processors are peers
multiprocessing (No Master Slave relation)
DISTRIBUTED SYSTEM
• Heterogeneous ,
physically separated
computer system are
networked together.
• Shares resources.
• Act as centralised OS
Types of Distributed OS
1. Client Server 2. Peer - to – Peer System:
3. Middleware 4. 3 – tier & N- tier
Interoperability of application running on different OS
Development made more easier.
Client data stored in intermediate tier.
REAL TIME OS (RTOS)
• A software component that rapidly switches b/w tasks.
• Used for real time computing applications that processes data and events that
have critically defined time constraints.
• RTOS :- event driven and preemptive.
• 2 key features:
1. Deterministic 2. Predictability
HARD RTOS SOFT RTOS FRIM RTOS
It is designed to provide deterministic It is designed to provide timely Designed to provide timely
response times to critical tasks or events. responses to tasks or events, but responses to tasks or events with a
with a degree of flexibility regarding guarantee of meeting deadlines
the timing constraints. most of the time.
Tasks have strict deadlines that must be Aim to achieve timely responses to Occasional missed deadlines may
met, any failure to meet these deadlines events whenever possible, but be tolerated under certain
could result in system failure or occasional missed deadlines may conditions.
unacceptable performance degradation. be acceptable if they do not
compromise system functionality or
safety.
Hard RTOS are commonly used in Provide a balance between These systems offer a balance
applications where timing predictability responsiveness and flexibility, between predictability and flexibility,
and reliability are paramount making them suitable for a wide ensuring reliable performance in
range of applications where demanding real-time environments.
occasional delays are tolerable as
long as they do not compromise
system functionality or user
experience.
Applications : Applications: Applications:
• Aerospace and Defense • Gaming Consoles Financial Trading Systems
• Industrial Automation • Multimedia Systems Power Grid Control
• Medical Devices • Embedded Systems Aerospace and Defense Systems
• Automotive • Automotive Infotainment Industrial Control Systems
• Robotics
