This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
developersguide:userspacescheduling [2017/06/02 16:26] shtjonathan [How does it work?] |
developersguide:userspacescheduling [2017/06/02 16:31] (current) shtjonathan [Advantages over the in-kernel scheduler] minor syntax edits |
||
---|---|---|---|
Line 11: | Line 11: | ||
==== Advantages over the in-kernel scheduler ==== | ==== Advantages over the in-kernel scheduler ==== | ||
- | No need to make any changes in the kernel if a different scheduling policy is required. The ability to change the priority and time quantum allows implementation of wide range of scheduling algorithms | + | No need to make any changes in the kernel if a different scheduling policy is required. The ability to change the priority and time quantum allows implementation of a wide range of scheduling algorithms |
==== Current status ==== | ==== Current status ==== | ||
SCHED is the //userspace// scheduler for most processes. The some core system processes are scheduled by kernel using the default policy. You can find the details of the design and implementation in the projects final [[http://www.minix3.org/docs/scheduling/report.pdf|report]] by Bjorn Swift | SCHED is the //userspace// scheduler for most processes. The some core system processes are scheduled by kernel using the default policy. You can find the details of the design and implementation in the projects final [[http://www.minix3.org/docs/scheduling/report.pdf|report]] by Bjorn Swift | ||