Uploaded byDr. C.V. Suresh Babu
Process scheduling linux
Linux uses a preemptive multilevel feedback queue scheduling algorithm. Processes have both static priorities based on nice values and dynamic priorities based on recent CPU usage. The scheduler selects from two lists of active and expired processes using their dynamic priorities. It also performs load balancing across CPU runqueues to improve performance on multiprocessor systems. System calls like setpriority(), sched_setscheduler(), and sched_yield() allow modifying process priorities and scheduling policies.
More Related Content
Similar to Process scheduling linux
More from Dr. C.V. Suresh Babu
Process scheduling linux
- 1.
- 2. Outline Scheduling PolicyScheduling Algorithm System Calls related to Scheduling
- 3. Scheduling Policy Basedon time-sharing Time slice Based on priority ranking Dynamic Classification of processes Interactive processes Batch processes Real-time processes
- 4. System Calls relatedto Scheduling change the priority get the maximum group priority set the group priority get the scheduling policy set the scheduling policy and priority get the priority set the priority relinquish the processor voluntarily get the minimum priority value get the maximum priority value get the time quantum for Round-Robin set the CPU affinity mask get the CPU affinity mask nice() getpriority() setpriority() sched_getscheduler() sched_setscheduler() sched_getparam() sched_setparam() sched_yield() sched_get_priority_min() sched_get_priority_max() sched_rr_get_interval() sched_setaffinity() sched_getaffinity() description System call
- 5. Process Preemption Linux(user) processes are preemptive When a new process has higher priority than the current When its time quantum expires, TIF_NEED_RESCHED will be set A preempted process is not suspended since it remains in the TASK_RUNNING state Linux kernel before 2.5 is nonpreemptive Simpler Linux kernel 2.6 is preemptive
- 6. How Long Musta Quantum Last? Neither too long nor too short Too short: overhead for process switch Too long: processes no longer appear to be executed concurrently Always a compromise The rule of thumb: to choose a duration as long as possible, while keeping good system response time
- 7. The Scheduling AlgorithmEarlier version of Linux: simple and straightforward At every process switch, scan the runnable processes, compute the priorities, and select the best to run Much more complex in Linux 2.6 Scales well with the number of processes and processors Constant time scheduling 3 Scheduling classes SCHED_FIFO: First-In First-Out real-time SCHED_RR: Round-Robin real-time SCHED_ NORMAL : conventional time-shared processes
- 8. Scheduling of ConventionalProcesses Static priority Conventional processes: 100-139 Can be changed by nice(), setpriority() system calls Base time quantum : the time-quantum assigned by the scheduler if it has exhausted its previous time quantum
- 9. Typical Priority Valuesfor a Conventional Process 1199 ms +6 5 ms +19 139 Lowest static priority 999 ms +4 50 ms +10 130 Low static priority 799 ms +2 100 ms 0 120 Default static priority 499 ms - 1 600 ms - 10 110 High static priority 299 ms -3 800 ms -20 100 Highest static priority Sleep time threshold Interactive delta Base time quantum Nice value Static priority Description
- 10. Dynamic Priority andAverage Sleep Time Dynamic priority: 100-139 Dynamic priority = max (100, min( static_priority – bonus + 5 , 139) ) Bonus: 0-10 <5: penalty >5: premium Dependent on the average sleep time Average number of nanoseconds that the process spent while sleeping
- 11. Average Sleep Time,Bonus Values, and Time Slice Granularity 10 10 1 second 10 9 >= 900 ms but < 1000 ms 20 8 >= 800 ms but < 900 ms 40 7 >= 700 ms but < 800 ms 80 6 >= 600 ms but < 700 ms 160 5 >= 500 ms but < 600 ms 320 4 >= 400 ms but < 500 ms 640 3 >= 300 ms but < 400 ms 1280 2 >= 200 ms but < 300 ms 2560 1 >= 100 ms but < 200 ms 5120 0 >= 0 but < 100 ms Granularity Bonus Average sleep time
- 12. To determine whethera process is considered interactive or batch Interactive if: dynamic_priority <= 3* static_priority/4+28 Bonus-5 >= static_priority/4-28 interactive delta
- 13. Active and ExpiredProcesses Active processes : runnable processes that have not exhausted their time quantum Expired processes : runnable processes that have exhausted their time quantum Periodically, the role of processes changes
- 14. Scheduling on Real-TimeProcesses Real time priority: 1-99 Real-time processes are always considered active Can be changed by sched_setparam() and sched_setscheduler() system calls A real-time process is replaced only when Another process has higher real-time priority Put to sleep by blocking operation Stopped or killed Voluntarily relinquishes the CPU by sched_yield() system call For round-robin real-time (SCHED_RR), time quantum exhausted
- 15. Data Structures Usedby the Scheduler runqueue data structure for each CPU lock: spin lock nr_running: number of runnable processes cpu_load nr_switches: number of process switches nr_uninterruptable expired_timestamp timestamp_last_tick curr: process descriptor pointer of the currently running process idle: prev_mm active: pointer to the list of active processes expired: pointer to the list of expired processes arrays: two sets of active of expired processes best_expired_prio nr_iowait sd active_balance push_cpu migration_thread migration_queue
- 16. Two Sets ofRunnable Processes in the runqueue Structure
- 17. Process Descriptor FieldsRelated to the Scheduler thread_info->flags thread_info->cpu state prio static_prio run_list array sleep_avg timestamp last_ran activated policy cpus_allowed time_slice first_time_slice rt_priority
- 18. Functions Used bythe Scheduler scheduler_tick(): keep the time_slice counter up-to-date try_to_wake_up(): awaken a sleeping process recalc_task_prio(): updates the dynamic priority schedule(): select a new process to run load_balance(): keep the runqueue of multiprocess system balanced (…Details ignored…)
- 19. The schedule() FunctionDirect invocation When the process must be blocked to wait for resource When long iterative tasks are executed in device drivers Lazy invocation: by setting the TIF_NEED_RESCHED flag When current has used up its quantum, by scheulertick() When a process is woken up, by try_to_wake_up() When a sched_setscheduler() system call is issued Actions performed by schedule() before and after a process switch (…Details ignored…)
- 20. Runqueue Balancing inMultiprocessor Systems 3 types of multiprocessor systems Classic multiprocessor architecture Hyper-threading NUMA A CPU can execute only the runnable processes in the corresponding runqueue The kernel periodically checks if the workloads of the runqueues are balanced
- 21. Scheduling Domains Schedulingdomain: a set of CPUs whose workloads are kept balanced bt the kernel Hierarchically organized Partitioned into groups: a subset of CPUs
- 22. System Calls Relatedto Scheduling nice(): for backward compatibility only Allows processed to change their base priority Replaced by setpriority() getpriority() and setpriority() Act on the base priorities of all processes in a given group which: PRIO_PROCESS, PRIO_PGRP, PRIO_USER who: the value of pid, pgrp, or uid field to be used for selecting the processes niceval: the new base priority value: -20 - +19 sched_getaffinity() and sched_setaffinity() The bitmask of the CPUs that are allowed to run the process
- 23. System Calls Relatedto Real-Time Processes sched_getscheduler(), sched_setscheduler() Queries/sets the scheduling policy sched_getparam(), sched_setparam() Retrieves/sets the scheduling parameters sched_yield() To relinquish the CPI voluntarily without being suspended sched_get_priority_min(), sched_get_priority_max() To return the minimum/maximum real-time static priority sched_rr_get_interval() To write into user space the round-robin time quantum for real-time process