Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Rate-monotonic scheduling
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Upper bound for harmonic task sets === Liu and Layland noted that this bound may be relaxed to the maximum possible value of 1.0, if for tasks <math>{T_m}</math>, <math>{T_i}</math> where <math>{T_m} {>} {T_i}</math> and <math>i = 1...m-1</math>, <math>{T_m}</math> is an integer multiple of <math>{T_i}</math>, which is to say that all tasks have a period that is not just a multiple of the shortest period, <math>{T_1}</math>, but instead that any task's period is a multiple of all shorter periods. This is known as an [[Harmonic Task Set|harmonic task set]]. An example of this would be: <math>[{T_1},{T_2},{T_3},{T_4}] = [1, 3, 6, 12]</math>. It is acknowledged by Liu and Layland that it is not always feasible to have a harmonic task set and that in practice other mitigation measures, such as buffering for tasks with soft-time deadlines or using a dynamic priority assignment approach may be used instead to allow for a higher bound.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)