Process Scheduling 1 Chapter 5. Process Scheduling Clock interrupt handling Scheduler goal Traditional UNIX scheduling SVR4 scheduler Solaris 2.x scheduling enhancements Scheduling in Mach Other scheduling implementation

Process Scheduling 2 Clock Interrupt Handling H/W clock interrupts the system at fixed time intervals The clock interrupt handler is second priority only to that of power-failure interrupt The clock interrupt handler performs –rearms the h/w clock if necessary –updates CPU usage statistics for the current process

Process Scheduling 3 Clock Interrupt Handling (cont) –performs scheduler-related functions, such as priority recomputation time-slice expiration handling –sends a SIGXCPU signal to the current process if it has exceeded its CPU usage quota –updates the time-of-day clock and other related clocks –handle callouts –wakes up system processes such as the swapper and pagedaemon when appropriate –handle alarm

Process Scheduling 4 Callouts A callout records a function that the kernel must invoke at a later time –e.g. SVR4 –int to_ID = timeout(void (*fn( )), caddr_t arg, long delta); In system context Used for periodic tasks –retransmission of network packets –scheduler and memory management functions –monitoring devices to avoid losing interrupts –polling devices that do not support interrupts

Process Scheduling 5 Callouts (cont) Callout implementation in BSD UNIX Callout listhead t = 2 roundrobin t = 1 schedcpu t = 4 f1 t = 0 f2 time left to fire2377 (a) Callout queue at on instant of time Callout listhead t = 1 roundrobin t = 1 schedcpu t = 4 f1 t = 0 f2 time left to fire1266 (b) Callout queue one tick later

Process Scheduling 6 Alarms A process requests the kernel to send it a signal after a specific amount of time three types of alarms –real-time alarm relates to the actual elapsed time, via a SIGALARM signal high resolution  high accuracy –profiling alarm measures the amount of time the process has been executing, via SIGPROF signal –virtual time alarm monitors only the time spent by the process in user mode, via SIGVTALARM signal

Process Scheduling 7 Scheduler Goals Deliver acceptable performance to each Ap. Categories of applications –interactive spend a lot of time waiting user input system needs to reduce the average time and variance btw user action and application response acceptable delay is about 50 ~ 150ms –batch do not require user interaction, as background jobs criteria: task’s completion time –real-time time-critical with guaranteed bounds on response time

Process Scheduling 8 Traditional Scheduling SVR3, 4.3 BSD Scheduling target –time-sharing, interactive environment with several batch and foreground processes simultaneously Scheduling policy –improve response time of interactive users, while ensuring that low priority, background jobs do not starve

Process Scheduling 9 Traditional Scheduling (cont) Priority-based –priority changes with time –preemptive time-slicing Kernel is nonpreemptible Process priority –0 ~ 49: kernel, 50 ~ 127: process in user mode proc structure –p_pricurrent scheduling priority –p_usrpriuser mode priority –p_cpumeasure of recent CPU usage –p_niceuser-controllable nice factor

Process Scheduling 10 Traditional Scheduling (cont) Sleep priority –kernel value (0 ~ 49) –e.g. terminal input: 28, disk I/O: 20 Priority calculation: schedcpu( ) –every tick, clock handler increments p_cpu for the current process –every second, p_cpu = p_cpu - decay factor; –p_usrpri = PUSER + p_cpu/4 + 2*p_nice; –PUSER is the baseline priority of 50

Process Scheduling 11 Traditional Scheduling (cont) Scheduler implementation 00 0 ~ 3 4 ~ 7 8 ~ ~ ~ ~23... P whichqs PP PP 0110 qs...

Process Scheduling 12 Traditional Scheduling (cont) Situations for context switch –current process blocks on a resource, or exits –priority recomputation procedure results in the priority of another process becoming greater than that of of the current one –current process, or an interrupt handler, wakes up a higher-priority process

Process Scheduling 13 Traditional Scheduling (cont) Analysis –simple and effective –favor I/O-bound jobs –not scale well –no guarantee of CPU usage and response time –kernel is non-preemptive: priority inversion

Process Scheduling 14 SVR4 Scheduler Scheduling class –time sharing and real-time class-independent routines –common services such as context switching, run queue manipulation, and preemption class-dependent routines –priority computation and inheritance

Process Scheduling 15 SVR4 Scheduler (cont) SVR4 dispatch queues P dqactmap PP PP 1010 dispq...

Process Scheduling 16 SVR4 Scheduler (cont) SVR4 kernel defines several preemption points –places in the kernel code where all kernel data structures are in a stable state, and the kernel is about to embark on a length computation Three ranges of 160 priorities –0 ~ 59: time-sharing class –60 ~ 99: system priorities –100 ~ 159: real-time class

Process Scheduling 17 SVR4 Scheduler (cont) interface to the scheduling class real-time time-sharing system rt_classfuncs rt-init sys_classfuncs ts_classfuncs Global class table sys-init ts-init p_cid p_clfuncs p_clproc... p_cid p_clfuncs p_clproc... p_cid p_clfuncs p_clproc... p_cid p_clfuncs p_clproc... class-dependent data class-dependent data class-dependent data class-dependent data proc structures

Process Scheduling 18 SVR4 Scheduler (cont) Time-sharing class –changes process priorities dynamically –round-robin scheduling with the same priority –event driven scheduling reduces process priority each time it uses up its time slice boosts the priority of the process if it blocks on an event or resource, or if it takes a long time to use up it quantum

Process Scheduling 19 SVR4 Scheduler (cont) Real-time class –scheduled before any kernel process –fixed priority and time quantum –requires bounded dispatch latency and response time Interrupt processing nonpreemptive kernel processing context switch application code event occurs process made runnable context switch initiated process is scheduled to run process responds to event time dispatch latency response time

Process Scheduling 20 SVR4 Scheduler (cont) Analysis –allows the addition of scheduling class –time-sharing class changes priorities based on events related to that process –favor I/O-bound and interactive jobs over CPU- bound ones –code path btw preemption points is too long for time-critical applications –difficult to tune the system properly for a mixed set of jobs

Process Scheduling 21 Solaris 2.x Scheduling Enhancement Preemptive kernel –most global kernel data structures must be protected by synchronization objects –implementation of interrupts using special kernel threads Multiprocessor support –single dispatch queue for all processors

Process Scheduling 22 MP Scheduling in Solaris 2.x Initial situation P1P2P3P4P5 T1 pri 120 T2 pri 130 T3 pri 100 T4 pri 132 T5 pri 135 T6 pri 130 T7 pri 115

Process Scheduling 23 MP Scheduling in Solaris (cont) After T6 and T7 become runnable P1P2P3P4P5 T1 pri 120 T2 pri 130 T3 pri 100 T4 pri 132 T5 pri 135 about to be switched out CPU_chosen_level = 130 T6 pri 130 T7 pri 115 dispatcher queues about to be scheduled on P3

Process Scheduling 24 Priority Inversion Lower priority process holds a resource needed by a higher priority process, thereby blocking that higher priority process Solved by priority inheritance –when a high-priority thread blocks on a resource, it temporarily transfer its priority to the lower priority thread that owns the resource

Process Scheduling 25 Priority Inversion (cont) T1 pri 100 currently running holdsblocks T2 pri 130 T3 pri 110 becomes runnable (a) Initial situation (b) Without priority inheritance (c) With priority inheritance T1 pri 100 runnable holdsblocks T2 pri 130 T3 pri 110 currently running dispatcher queues T1 pri 100 runnable holdsblocks T2 pri 130 T3 pri 110 dispatcher queues currently running inh pri = 130 R R R

Process Scheduling 26 Priority Inversion (cont) Transitive priority inheritance T6 pri 100 currently running holdsblocks T5 pri 110 R1 (a) Initial situation holdsblocks T4 pri 135 R2 T7 pri 122 becomes runnable T6 pri 100 currently running holdsblocks T5 pri 110 R1 (b) Transitive priority inheritance holdsblocks T4 pri 135 R2 T7 pri 122 runnable inh pri = 135 dispatcher queues

Process Scheduling 27 Priority Inheritance Traversing the synchronization chain currently running T4 gp 100 runnable blocked threads R1 T5 gp 80 R2R3R4 T1 gp 60 ip 100 T6 gp 110 T2 gp 90 ip 100 T3 gp 70 holds owner holds wants owner holds owner gp = global priority ip = inherited priority

Process Scheduling 28 Priority Inheritance (cont) currently running T4 gp 100 blocked threads R1 T5 gp 80 ip 110 R2R3R4 T1 gp 60 ip 110 T6 gp 110 T2 gp 90 ip 100 T3 gp 70 holds owner holds owner holds owner gp = global priority ip = inherited priority

Process Scheduling 29 Priority Inheritance (cont) Limitations –is not used for semaphores and condition variables since the owner is usually indeterminate Turnstiles –reduce information maintained by kernel for hundreds of synchronization objects Turnstile pool T T T T T T active Blocked threads Synchronization objects active

Process Scheduling 30 Scheduling in Mach Schedules threads regardless of the task to which they belong Handoff scheduling –a thread can directly yield the processor to another thread w/o searching the run queue –improves the performance of the IPC calls Multiprocessor support –processor allocation can be handled by a user-lever server program –gang scheduling

Process Scheduling 31 Other Scheduling Deadline-driven scheduling Three-level scheduler –isochronous class –real-time class –general-purpose class –admission control