Run-to-completion scheduling: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m Task 18 (cosmetic): eval 1 template: del empty params (1×);
BattyBot (talk | contribs)
Line 1:
{{unreferencedmore citations needed|date=DecemberJanuary 20122021}}
 
'''Run-to-completion scheduling''' or '''nonpreemptive scheduling''' is a [[scheduling (computing)|scheduling]] model in which each task runs until it either finishes, or explicitly yields control back to the scheduler.<ref>{{Cite book|title=Modern operating systems.|last=Tanenbaum|first=Andrew S.|publisher=Pearson|year=2015|isbn=9780133591620|edition=4th|pages=153|oclc=870646449}}</ref> Run to completion systems typically have an [[event queue]] which is serviced either in strict order of admission by an [[event loop]], or by an [[admission scheduler]] which is capable of scheduling events out of order, based on other constraints such as [[time limit|deadlines]].