Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Chapter 5: CPU Scheduling
5.2 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Chapter 5: CPU Scheduling
 Basic Concepts
 Scheduling Criteria
 Scheduling Algorithms
 Thread Scheduling
 Multiple-Processor Scheduling
 Operating Systems Examples
5.3 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Objectives
 To introduce CPU scheduling, which is the basis for multiprogrammed operating
systems
 To describe various CPU-scheduling algorithms
 To discuss evaluation criteria for selecting a CPU-scheduling algorithm for a
particular system
5.4 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
CPU Scheduling
 Operating System manages a collection of processes.
 If a system has more processes and one CPU or More processes with fewer
CPU’s has to divide CPU time among different processes.
 This is called CPU scheduling.
5.5 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Basic Concepts
 Maximum CPU utilization obtained with multiprogramming
 OS can make the computer more productive by switching the CPU
among processes.
 Main objective is some process running at all times
 CPU–I/O Burst Cycle – Process execution consists of a cycle of CPU
execution and I/O wait
 CPU burst distribution
5.6 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Alternating Sequence of CPU and
I/O Bursts
5.7 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
CPU Scheduler
 Selects from among the processes in ready queue, and allocates the CPU to
one of them
 Queue may be ordered in various ways
 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 under 1 and 4 is nonpreemptive
 All other scheduling is preemptive
 Preemption means that a process may be forcibly removed from the CPU
even if it does not want to release the CPU.
5.8 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
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
5.9 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Different CPU-scheduling algorithms have different
properties, and the choice of a particular algorithm may
favor one class of processes over another. In choosing
which algorithm to use in a particular situation, we must
consider the properties of the various algorithms.
Many criteria have been suggested for comparing CPU-
scheduling algorithms.
Scheduling Criteria
5.10 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Scheduling Criteria
The criteria include the following:
 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 was submitted
until the first response is produced, not output.
5.11 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Scheduling Algorithm Optimization Criteria
 Max CPU utilization
 Max throughput
 Min turnaround time
 Min waiting time
 Min response time
5.12 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
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:
 Waiting time for P1 = 0; P2 = 24; P3 = 27
 Average waiting time: (0 + 24 + 27)/3 = 17
P1 P2 P3
24 27 300
5.13 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
FCFS Scheduling (Cont.)
Suppose that the processes arrive in the order:
P2 , P3 , P1
 The Gantt chart for the schedule is:
 Waiting time for P1 = 6; P2 = 0; P3 = 3
 Average waiting time: (6 + 0 + 3)/3 = 3
 Much better than previous case
 Convoy effect - short process behind long process
 Consider one CPU-bound and many I/O-bound processes
P1P3P2
63 300
5.14 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
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
 SJF is optimal – gives minimum average waiting time for a given
set of processes
 The difficulty is knowing the length of the next CPU request
 Could ask the user
5.15 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Example of SJF
ProcessArrival Time Burst Time
P1 0.0 6
P2 2.0 8
P3 4.0 7
P4 5.0 3
 SJF scheduling chart
 Average waiting time = (3 + 16 + 9 + 0) / 4 = 7
P4
P3P1
3 160 9
P2
24
5.16 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Example of Shortest-remaining-time-first
 Now we add the concepts of varying arrival times and preemption to the analysis
ProcessA arri Arrival TimeT Burst Time
P1 0 8
P2 1 4
P3 2 9
P4 3 5
 Preemptive SJF Gantt Chart
 Average waiting time = [(10-1)+(1-1)+(17-2)+5-3)]/4 = 26/4 = 6.5 msec
P1
P1P2
1 170 10
P3
265
P4
5.17 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Priority Scheduling
 A priority number (integer) is associated with each process
 The CPU is allocated to the process with the highest priority (smallest integer 
highest priority)
 Preemptive
 Nonpreemptive
 SJF is priority scheduling where priority is the inverse of predicted next CPU
burst time
 Problem  Starvation – low priority processes may never execute
 Solution  Aging – as time progresses increase the priority of the process
5.18 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Example of Priority Scheduling
ProcessA arri Burst TimeT Priority
P1 10 3
P2 1 1
P3 2 4
P4 1 5
P5 5 2
 Priority scheduling Gantt Chart
 Average waiting time = 8.2 msec
P2 P3P5
1 180 16
P4
196
P1
5.19 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Example of Priority Scheduling
5.20 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Round Robin (RR)
 Each process gets a small unit of CPU time (time quantum q),
usually 10-100 milliseconds. After this time has elapsed, the
process is preempted and added to the end of the ready queue.
 If there are n processes in the ready queue and the time quantum is
q, then each process gets 1/n of the CPU time in chunks of at most
q time units at once. No process waits more than (n-1)q time units.
 Timer interrupts every quantum to schedule next process
 Performance
 q large  FIFO
 q small  q must be large with respect to context switch,
otherwise overhead is too high
5.21 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Example of RR with Time Quantum = 4
Process Burst Time
P1 24
P2 3
P3 3
 The Gantt chart is:
 Typically, higher average turnaround than SJF, but better response
 q should be large compared to context switch time
 q usually 10ms to 100ms, context switch < 10 us sec
P1 P2 P3 P1 P1 P1 P1 P1
0 4 7 10 14 18 22 26 30
5.22 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Time Quantum and Context Switch Time
5.23 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Turnaround Time Varies With
The Time Quantum
80% of CPU bursts should
be shorter than q
5.24 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Multilevel Queue
 Ready queue is partitioned into separate queues, eg:
 foreground (interactive)
 background (batch)
 Process permanently in a given queue
 Each queue has its own scheduling algorithm:
 foreground – RR
 background – FCFS
 Scheduling must be done between the queues:
 Fixed priority scheduling; (i.e., serve all from foreground then from
background). Possibility of starvation.
 Time slice – each queue gets a certain amount of CPU time which it can
schedule amongst its processes; i.e., 80% to foreground in RR
 20% to background in FCFS
5.25 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Multilevel Queue Scheduling
5.26 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Multilevel Feedback Queue
 A process can move between the various queues; aging can be
implemented this way
 Multilevel-feedback-queue scheduler defined by the following parameters:
 number of queues
 scheduling algorithms for each queue
 method used to determine when to upgrade a process
 method used to determine when to demote a process
 method used to determine which queue a process will enter when that
process needs service
5.27 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Example of Multilevel Feedback Queue
 Three queues:
 Q0 – RR with time quantum 8 milliseconds
 Q1 – RR time quantum 16 milliseconds
 Q2 – FCFS
 Scheduling
 A new job enters queue Q0 which is served FCFS
 When it gains CPU, job receives 8 milliseconds
 If it does not finish in 8 milliseconds, job is moved to queue Q1
 At Q1 job is again served FCFS and receives 16 additional milliseconds
 If it still does not complete, it is preempted and moved to queue Q2
5.28 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Multilevel Feedback Queues
5.29 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
Multiple-Processor Scheduling
 CPU scheduling more complex when multiple CPUs are available
 Homogeneous processors within a multiprocessor
 Asymmetric multiprocessing – only one processor accesses the system data
structures, alleviating the need for data sharing. Other executing user code.
 Symmetric multiprocessing (SMP) – each processor is self-scheduling, all
processes in common ready queue, or each has its own private queue of ready
processes
 Currently, most common
 Processor affinity – process has affinity for processor on which it is currently
running. Most systems try to avoid migration of processes from one processor
to another and instead attempt to keep a process running on the same
processor.
 soft affinity
 hard affinity it is possible for a process to migrate between processors.
5.30 Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8th Edition
NUMA and CPU Scheduling
non-uniform memory access

cpu scheduling

  • 1.
    Silberschatz, Galvin andGagne ©2009Operating System Concepts – 8th Edition Chapter 5: CPU Scheduling
  • 2.
    5.2 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Chapter 5: CPU Scheduling  Basic Concepts  Scheduling Criteria  Scheduling Algorithms  Thread Scheduling  Multiple-Processor Scheduling  Operating Systems Examples
  • 3.
    5.3 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Objectives  To introduce CPU scheduling, which is the basis for multiprogrammed operating systems  To describe various CPU-scheduling algorithms  To discuss evaluation criteria for selecting a CPU-scheduling algorithm for a particular system
  • 4.
    5.4 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition CPU Scheduling  Operating System manages a collection of processes.  If a system has more processes and one CPU or More processes with fewer CPU’s has to divide CPU time among different processes.  This is called CPU scheduling.
  • 5.
    5.5 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Basic Concepts  Maximum CPU utilization obtained with multiprogramming  OS can make the computer more productive by switching the CPU among processes.  Main objective is some process running at all times  CPU–I/O Burst Cycle – Process execution consists of a cycle of CPU execution and I/O wait  CPU burst distribution
  • 6.
    5.6 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Alternating Sequence of CPU and I/O Bursts
  • 7.
    5.7 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition CPU Scheduler  Selects from among the processes in ready queue, and allocates the CPU to one of them  Queue may be ordered in various ways  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 under 1 and 4 is nonpreemptive  All other scheduling is preemptive  Preemption means that a process may be forcibly removed from the CPU even if it does not want to release the CPU.
  • 8.
    5.8 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition 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
  • 9.
    5.9 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Different CPU-scheduling algorithms have different properties, and the choice of a particular algorithm may favor one class of processes over another. In choosing which algorithm to use in a particular situation, we must consider the properties of the various algorithms. Many criteria have been suggested for comparing CPU- scheduling algorithms. Scheduling Criteria
  • 10.
    5.10 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Scheduling Criteria The criteria include the following:  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 was submitted until the first response is produced, not output.
  • 11.
    5.11 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Scheduling Algorithm Optimization Criteria  Max CPU utilization  Max throughput  Min turnaround time  Min waiting time  Min response time
  • 12.
    5.12 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition 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:  Waiting time for P1 = 0; P2 = 24; P3 = 27  Average waiting time: (0 + 24 + 27)/3 = 17 P1 P2 P3 24 27 300
  • 13.
    5.13 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition FCFS Scheduling (Cont.) Suppose that the processes arrive in the order: P2 , P3 , P1  The Gantt chart for the schedule is:  Waiting time for P1 = 6; P2 = 0; P3 = 3  Average waiting time: (6 + 0 + 3)/3 = 3  Much better than previous case  Convoy effect - short process behind long process  Consider one CPU-bound and many I/O-bound processes P1P3P2 63 300
  • 14.
    5.14 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition 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  SJF is optimal – gives minimum average waiting time for a given set of processes  The difficulty is knowing the length of the next CPU request  Could ask the user
  • 15.
    5.15 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Example of SJF ProcessArrival Time Burst Time P1 0.0 6 P2 2.0 8 P3 4.0 7 P4 5.0 3  SJF scheduling chart  Average waiting time = (3 + 16 + 9 + 0) / 4 = 7 P4 P3P1 3 160 9 P2 24
  • 16.
    5.16 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Example of Shortest-remaining-time-first  Now we add the concepts of varying arrival times and preemption to the analysis ProcessA arri Arrival TimeT Burst Time P1 0 8 P2 1 4 P3 2 9 P4 3 5  Preemptive SJF Gantt Chart  Average waiting time = [(10-1)+(1-1)+(17-2)+5-3)]/4 = 26/4 = 6.5 msec P1 P1P2 1 170 10 P3 265 P4
  • 17.
    5.17 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Priority Scheduling  A priority number (integer) is associated with each process  The CPU is allocated to the process with the highest priority (smallest integer  highest priority)  Preemptive  Nonpreemptive  SJF is priority scheduling where priority is the inverse of predicted next CPU burst time  Problem  Starvation – low priority processes may never execute  Solution  Aging – as time progresses increase the priority of the process
  • 18.
    5.18 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Example of Priority Scheduling ProcessA arri Burst TimeT Priority P1 10 3 P2 1 1 P3 2 4 P4 1 5 P5 5 2  Priority scheduling Gantt Chart  Average waiting time = 8.2 msec P2 P3P5 1 180 16 P4 196 P1
  • 19.
    5.19 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Example of Priority Scheduling
  • 20.
    5.20 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Round Robin (RR)  Each process gets a small unit of CPU time (time quantum q), usually 10-100 milliseconds. After this time has elapsed, the process is preempted and added to the end of the ready queue.  If there are n processes in the ready queue and the time quantum is q, then each process gets 1/n of the CPU time in chunks of at most q time units at once. No process waits more than (n-1)q time units.  Timer interrupts every quantum to schedule next process  Performance  q large  FIFO  q small  q must be large with respect to context switch, otherwise overhead is too high
  • 21.
    5.21 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Example of RR with Time Quantum = 4 Process Burst Time P1 24 P2 3 P3 3  The Gantt chart is:  Typically, higher average turnaround than SJF, but better response  q should be large compared to context switch time  q usually 10ms to 100ms, context switch < 10 us sec P1 P2 P3 P1 P1 P1 P1 P1 0 4 7 10 14 18 22 26 30
  • 22.
    5.22 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Time Quantum and Context Switch Time
  • 23.
    5.23 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Turnaround Time Varies With The Time Quantum 80% of CPU bursts should be shorter than q
  • 24.
    5.24 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Multilevel Queue  Ready queue is partitioned into separate queues, eg:  foreground (interactive)  background (batch)  Process permanently in a given queue  Each queue has its own scheduling algorithm:  foreground – RR  background – FCFS  Scheduling must be done between the queues:  Fixed priority scheduling; (i.e., serve all from foreground then from background). Possibility of starvation.  Time slice – each queue gets a certain amount of CPU time which it can schedule amongst its processes; i.e., 80% to foreground in RR  20% to background in FCFS
  • 25.
    5.25 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Multilevel Queue Scheduling
  • 26.
    5.26 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Multilevel Feedback Queue  A process can move between the various queues; aging can be implemented this way  Multilevel-feedback-queue scheduler defined by the following parameters:  number of queues  scheduling algorithms for each queue  method used to determine when to upgrade a process  method used to determine when to demote a process  method used to determine which queue a process will enter when that process needs service
  • 27.
    5.27 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Example of Multilevel Feedback Queue  Three queues:  Q0 – RR with time quantum 8 milliseconds  Q1 – RR time quantum 16 milliseconds  Q2 – FCFS  Scheduling  A new job enters queue Q0 which is served FCFS  When it gains CPU, job receives 8 milliseconds  If it does not finish in 8 milliseconds, job is moved to queue Q1  At Q1 job is again served FCFS and receives 16 additional milliseconds  If it still does not complete, it is preempted and moved to queue Q2
  • 28.
    5.28 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Multilevel Feedback Queues
  • 29.
    5.29 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition Multiple-Processor Scheduling  CPU scheduling more complex when multiple CPUs are available  Homogeneous processors within a multiprocessor  Asymmetric multiprocessing – only one processor accesses the system data structures, alleviating the need for data sharing. Other executing user code.  Symmetric multiprocessing (SMP) – each processor is self-scheduling, all processes in common ready queue, or each has its own private queue of ready processes  Currently, most common  Processor affinity – process has affinity for processor on which it is currently running. Most systems try to avoid migration of processes from one processor to another and instead attempt to keep a process running on the same processor.  soft affinity  hard affinity it is possible for a process to migrate between processors.
  • 30.
    5.30 Silberschatz, Galvinand Gagne ©2009Operating System Concepts – 8th Edition NUMA and CPU Scheduling non-uniform memory access