|
|
(One intermediate revision by one other user not shown) |
Line 1: |
Line 1: |
| {{Unreferenced|date=December 2009}}
| | Hello. Let me introduce the writer. Her name is Refugia Shryock. One of the extremely best issues in the globe for me is to do aerobics and I've been performing it for quite a while. Since she was eighteen she's been operating as a meter reader but she's usually wanted her own company. California is our beginning location.<br><br>Feel free to visit my web-site: [http://www.gigatronika.com/social/profile/LSmart home std test kit] |
| '''Least Slack Time''' (LST) scheduling is a [[scheduling algorithm]]. It assigns priority based on the ''slack time'' of a process. Slack time is the amount of time left after a job if the job was started now. This algorithm is also known as '''Least Laxity First'''. Its most common use is in embedded systems, especially those with multiple processors. It imposes the simple constraint that each process on each available processor possesses the same run time, and that individual processes do not have an affinity to a certain processor. This is what lends it a suitability to embedded systems.
| |
| | |
| ==Slack time==
| |
| This scheduling algorithm first selects those processes that have the smallest "slack time". Slack time is defined as the temporal difference between the deadline, the ready time and the run time.
| |
| | |
| More formally, the ''slack time'' for a process is defined as:
| |
| | |
| <math>(d - t) - c'</math>
| |
| | |
| where <math>d</math> is the process deadline, <math>t</math> is the real time since the cycle start, and <math>c'</math> is the remaining computation time.
| |
| | |
| ==Applications==
| |
| In Realtime Scheduling Algorithms for periodic jobs, an acceptance test is needed before accepting the sporadic jobs with its hard deadline. One of the simpliest acceptance test for the sporadic job is, calculating the sum amount of slack time between the realeasetime and deadline of the job.
| |
| | |
| ==Suitability==
| |
| LST scheduling is most useful in systems comprising mainly aperiodic tasks, because no prior assumptions are made on the events' rate of occurrence. The main weakness of LST is that it does not look ahead, and works only on the current system state. Thus, during a brief overload of system resources, LST can be sub-optimal. It will also be suboptimal when used with uninterruptible processes. However, like [[Earliest deadline first scheduling|earliest deadline first]], and unlike [[Rate-monotonic scheduling|rate monotonic scheduling]], this algorithm can be used for processor utilization up to 100%.
| |
| | |
| {{DEFAULTSORT:Least Slack Time Scheduling}}
| |
| [[Category:Scheduling algorithms]]
| |
Latest revision as of 04:41, 29 August 2014
Hello. Let me introduce the writer. Her name is Refugia Shryock. One of the extremely best issues in the globe for me is to do aerobics and I've been performing it for quite a while. Since she was eighteen she's been operating as a meter reader but she's usually wanted her own company. California is our beginning location.
Feel free to visit my web-site: home std test kit