sched.7: Minor fixes after review by Juri Lelli

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-05-13 19:55:13 +02:00
parent 6a6dd34494
commit 7bd7f43e80
1 changed files with 16 additions and 16 deletions

View File

@ -228,14 +228,14 @@ The following diagram clarifies these terms:
.in +4n
.nf
arrival/wakeup absolute deadline
| start time |
| | |
v v v
-----x--------xooooooooooooooooo-------x--------x---
arrival/wakeup absolute deadline
| start time |
| | |
v v v
-----x--------xooooooooooooooooo--------x--------x---
|<- comp. time ->|
|<------- relative deadline ----->|
|<-------------- period ------------------>|
|<------- relative deadline ------>|
|<-------------- period ------------------->|
.fi
.in
@ -258,14 +258,14 @@ scheduling, we have:
.in +4n
.nf
arrival/wakeup absolute deadline
| start time |
| | |
v v v
-----x--------xooooooooooooooooo-------x--------x---
|<-- Runtime --->|
|<----------- Deadline ---------->|
|<-------------- Period ------------------>|
arrival/wakeup absolute deadline
| start time |
| | |
v v v
-----x--------xooooooooooooooooo--------x--------x---
|<-- Runtime ------->|
|<----------- Deadline ----------->|
|<-------------- Period ------------------->|
.fi
.in
@ -295,7 +295,7 @@ The kernel requires that:
In addition, under the current implementation,
all of the parameter values must be at least 1024
(i.e., just over one microsecond,
which is the resolution of the implementation).
which is the resolution of the implementation), and less than 2^63.
If any of these checks fails,
.BR sched_setattr (2)
fails with the error