mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 03:01:39 -04:00
sched/dl/Documentation: Fix typos
Signed-off-by: Luca Abeni <[email protected]> Signed-off-by: Peter Zijlstra (Intel) <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Thomas Gleixner <[email protected]> Cc: [email protected] Cc: [email protected] Cc: [email protected] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Ingo Molnar <[email protected]>
This commit is contained in:
parent
3a3a58d406
commit
3aa2dbe27f
1 changed files with 2 additions and 2 deletions
|
|
@ -52,7 +52,7 @@ CONTENTS
|
|||
"admission control" strategy (see Section "4. Bandwidth management") is used
|
||||
(clearly, if the system is overloaded this guarantee cannot be respected).
|
||||
|
||||
Summing up, the CBS[2,3] algorithms assigns scheduling deadlines to tasks so
|
||||
Summing up, the CBS[2,3] algorithm assigns scheduling deadlines to tasks so
|
||||
that each task runs for at most its runtime every period, avoiding any
|
||||
interference between different tasks (bandwidth isolation), while the EDF[1]
|
||||
algorithm selects the task with the earliest scheduling deadline as the one
|
||||
|
|
@ -190,7 +190,7 @@ CONTENTS
|
|||
- deadline = D
|
||||
- period <= P
|
||||
|
||||
IOW, if runtime >= WCET and if period is >= P, then the scheduling deadlines
|
||||
IOW, if runtime >= WCET and if period is <= P, then the scheduling deadlines
|
||||
and the absolute deadlines (d_j) coincide, so a proper admission control
|
||||
allows to respect the jobs' absolute deadlines for this task (this is what is
|
||||
called "hard schedulability property" and is an extension of Lemma 1 of [2]).
|
||||
|
|
|
|||
Loading…
Reference in a new issue