Module 6: CPU Scheduling
Download
Report
Transcript Module 6: CPU Scheduling
Chapter 5: CPU Scheduling
Chapter 5: CPU Scheduling
Basic Concepts
Scheduling Criteria
Scheduling Algorithms
Multiple-Processor Scheduling
Real-Time Scheduling
Thread Scheduling
Operating Systems Examples
Java Thread Scheduling
Algorithm Evaluation
Operating System Concepts – 7th Edition, Feb 2, 2005
5.2
Silberschatz, Galvin and Gagne ©2005
Basic Concepts
Maximum CPU utilization obtained with
multiprogramming
CPU–I/O Burst Cycle – Process execution
consists of a cycle of CPU execution and I/O wait
CPU burst distribution: a large number of short
CPU bursts and a small number of large CPU
bursts
Operating System Concepts – 7th Edition, Feb 2, 2005
5.3
Silberschatz, Galvin and Gagne ©2005
Alternating Sequence of CPU And I/O Bursts
Operating System Concepts – 7th Edition, Feb 2, 2005
5.4
Silberschatz, Galvin and Gagne ©2005
Histogram of CPU-burst Times
Operating System Concepts – 7th Edition, Feb 2, 2005
5.5
Silberschatz, Galvin and Gagne ©2005
CPU Scheduler
Selects from among the processes in memory that are ready
to execute, and allocates the CPU to one of them
CPU scheduling decisions may take place when a process:
1. Switches from running to waiting state
2. Switches from running to ready state
3. Switches from waiting to ready
4. Terminates
Scheduling only under conditions 1 and 4 is nonpreemptive
or cooperative.
Scheduling under conditions 2 and 3 is preemptive
Operating System Concepts – 7th Edition, Feb 2, 2005
5.6
Silberschatz, Galvin and Gagne ©2005
CPU Scheduler
CPU scheduling conditions:
1. Process switches from running to waiting state
2. Process switches from running to ready state
3. Process switches from waiting to ready
4. Process terminates
Nonpreemptive or cooperative scheduling (1 and 4): Under
this type of scheduling, once the CPU has been allocated to
a process, the process keeps the CPU until it releases the
CPU either by terminating or by switching to the weighting
state (Windows 3.x).
Preemptive Scheduling (2 and 3): (Windows- 95, NT, 2000,
XP, Vista; Mac OS X, UNIX)
Operating System Concepts – 7th Edition, Feb 2, 2005
5.7
Silberschatz, Galvin and Gagne ©2005
Dispatcher
Dispatcher module gives control of the CPU to the process
selected by the short-term scheduler; this involves:
switching context
switching to user mode
jumping to the proper location in the user program to
restart that program
Dispatch latency – time it takes for the dispatcher to stop
one process and start another running
Operating System Concepts – 7th Edition, Feb 2, 2005
5.8
Silberschatz, Galvin and Gagne ©2005
Scheduling Criteria
CPU utilization – keep the CPU as busy as possible
Throughput – # of processes that complete their
execution per time unit
Turnaround time – amount of time to execute a
particular process
Waiting time – amount of time a process has been
waiting in the ready queue
Response time – amount of time it takes from when
a request (I/O )was submitted until the first response
is produced
Operating System Concepts – 7th Edition, Feb 2, 2005
5.9
Silberschatz, Galvin and Gagne ©2005
Optimization Criteria
Max CPU utilization
Max throughput
Min turnaround time
Min waiting time
Min response time
Operating System Concepts – 7th Edition, Feb 2, 2005
5.10
Silberschatz, Galvin and Gagne ©2005
Scheduling Algorithms
Operating System Concepts – 7th Edition, Feb 2, 2005
5.11
Silberschatz, Galvin and Gagne ©2005
First-Come, First-Served (FCFS) Scheduling
Process
Burst Time
P1
24
P2
3
P3
3
Suppose that the processes arrive in the order: P1 , P2 , P3
The Gantt Chart for the schedule is:
P1
P2
0
24
P3
27
30
Waiting time for P1 = 0; P2 = 24; P3 = 27
Average waiting time: (0 + 24 + 27)/3 = 17
Operating System Concepts – 7th Edition, Feb 2, 2005
5.12
Silberschatz, Galvin and Gagne ©2005
FCFS Scheduling (Cont.)
Suppose that the processes arrive in the order
P2 , P3 , P1
The Gantt chart for the schedule is:
P2
0
P3
3
P1
6
30
Waiting time for P1 = 6; P2 = 0; P3 = 3
Average waiting time: (6 + 0 + 3)/3 = 3
Much better than previous case
Convoy effect (one big CPU-bound process may force other
processes to wait for completion of its CPU burst if this big process
arrives first)
Hence, execution of short processes prior to a long process is
desirable
Operating System Concepts – 7th Edition, Feb 2, 2005
5.13
Silberschatz, Galvin and Gagne ©2005
Shortest-Job-First (SJF) Scheduling
Associate with each process the length of its next CPU
burst. Use these lengths to schedule the process with the
shortest time (the smallest next CPU burst).
Two schemes:
nonpreemptive – once CPU given to the process it
cannot be preempted until completes its CPU burst
preemptive – if a new process arrives with CPU burst
length less than remaining time of current executing
process, it can preempt the current process. This
scheme is known as the
Shortest-Remaining-Time-First (SRTF)
SJF is optimal if it gives minimum average waiting time for
a given set of processes
Operating System Concepts – 7th Edition, Feb 2, 2005
5.14
Silberschatz, Galvin and Gagne ©2005
Example of Non-Preemptive SJF
Process
Arrival Time
Burst Time
P1
0.0
7
P2
2.0
4
P3
4.0
1
P4
5.0
4
SJF (non-preemptive)
P1
0
3
P3
7
P2
8
P4
12
16
Average waiting time = (0 + 6 + 3 + 7)/4 = 4
Operating System Concepts – 7th Edition, Feb 2, 2005
5.15
Silberschatz, Galvin and Gagne ©2005
Example of Preemptive SJF
Shortest-Remaining-Time-First (SRTF)
Process
Arrival Time
Burst Time
P1
0.0
7
P2
2.0
4
P3
4.0
1
P4
5.0
4
SJF (preemptive)
P1
0
P2
2
P3
4
P2
5
P4
P1
11
7
16
Average waiting time = (9 + 1 + 0 +2)/4 = 3
Operating System Concepts – 7th Edition, Feb 2, 2005
5.16
Silberschatz, Galvin and Gagne ©2005
Determining Length of Next CPU Burst
Can only estimate the length
Can be done by using the length of previous CPU bursts, using
exponential averaging
1. tn actual length of nth CPU burst
2. n stores the past history
3. n 1 predicted value for the next CPU burst
4. , 0 1
5. Define:
tn
n 1
tn 1 n
contains the most recent information,
n
contains the past history
α is the relative weight of recent and past history; more commonly it is
taken α=1/2, so recent history and past history are equally weighted
Operating System Concepts – 7th Edition, Feb 2, 2005
5.17
Silberschatz, Galvin and Gagne ©2005
Philosophy of Exponential Averaging
=0
n+1 = n
Recent history does not count
=1
n+1 = tn
Only the actual last CPU burst counts
If we expand the formula, we get:
n+1 = tn+(1 - ) tn -1 + …
+(1 - )j tn -j + …
+(1 - )n +1 0
Since both and (1 - ) are less than or equal to 1, each
successive term has less weight than its predecessor
Operating System Concepts – 7th Edition, Feb 2, 2005
5.18
Silberschatz, Galvin and Gagne ©2005
Prediction of the Length of the Next CPU
Burst
n1 tn 1 n
0 10; 1/2; t0 6
Operating System Concepts – 7th Edition, Feb 2, 2005
5.19
Silberschatz, Galvin and Gagne ©2005