Talk:SCHED DEADLINE
| This is the talk page for discussing improvements to the SCHED DEADLINE article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||
| |||||||||||||||||||||
Explanation missing
editThe page does not reveal how the SCHED DEADLINE actually works, what tasks is it better at than CFQ and at what worse, there are also no tests of its usability. 77.180.199.255 (talk) 12:57, 22 January 2014 (UTC)
Weird first line
editI'm not perfectly competent about the kernel and CPU scheduling, but the first line:
"SCHED_DEADLINE is a scheduling class for resource-reservation real-time CPU scheduler in the Linux kernel."
Doesn't seem to make any damn sense. Am I wrong? How can something be for "resource-reservation real-time CPU scheduler"? Maybe it should read:
""SCHED_DEADLINE is a scheduling class for resource-reserving, real-time CPU scheduling in the Linux kernel."
Davidgumberg (talk) 16:55, 23 January 2014 (UTC)
- The term resource-reservation is jargon. This particular scheduler allows the user to specify a desired reservation, which, if available, is allocated to the user and removed from the OS's pool of unused resources. Hence, it belongs to a more general class of schedulers that guarantee correctness through a resource-reservation mechanism. This is in contrast to other schedulers that do not allow users to reserve resources and do not make any guarantees about system performance. For example, the other real-time scheduling classes in Linux– SCHED_FIFO and SCHED_RR– have no such reservation system. There, the user is free to create impossible scenarios so that the scheduler cannot guarantee good performance. 128.252.48.21 (talk) 21:14, 2 October 2015 (UTC)
Improved description of SCHED_DEADLINE
editI improved the description of SCHED_DEADLINE, created a new section with new details and references about how it works, and fixed a few statements that looked obsolete, as they were referring to the situation as before mainline integration.