This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
It is unclear where we can benefit from the deadline scheduler. I'm running my Ubuntu from a flashdisk (USB) and would like to know if this scheduling is an improvement on a USB disk (which has low read latency, but extremely high write and random R/W latency). It would be cool to mention if this sceduler is aimed for RAID, HD, SSD, SD or USB Flash or ....
This chapter uses "current batch" vs "active batch" without explaining what this means or what the difference is. Also, why wouldn't all batches be checked whether a request could be merged into it? — Preceding unsigned comment added by 80.146.191.154 (talk) 10:21, 18 December 2019 (UTC)
There is a piece of commercial software called Deadline (thinkboxsoftware.com) that is a render farm queue manager. Since both of these involve "scheduling" it might be helpful to provide some disambiguation. I'm not certain of the best way to approach that, but I figured I can at least bring it up. — Preceding unsigned comment added by Mmmancact (talk • contribs) 15:28, 15 September 2017 (UTC)
"Deadline scheduling" is a concept which has been around for decades – this Linux kernel component is just one implementation of it. We have an article discussing one particular theoretical version of it – Deadline-monotonic scheduling. But we have no coverage of other historically significant implementations, for example IBM mainframes, in particular JES3's implementation of deadline scheduling. I think either this article should be renamed to Deadline scheduler (Linux), or expanded to cover other historical instances. SomethingForDeletion (talk) 23:22, 11 May 2023 (UTC)