From d5034243faccb384a046e565d260b3db96754314 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Tue, 19 Dec 2017 10:22:09 +0100 Subject: [PATCH] sched.7: ffix Signed-off-by: Michael Kerrisk --- man7/sched.7 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/man7/sched.7 b/man7/sched.7 index 172940018..ea865b1d5 100644 --- a/man7/sched.7 +++ b/man7/sched.7 @@ -156,15 +156,15 @@ it will always immediately preempt any currently running algorithm without time slicing. For threads scheduled under the \fBSCHED_FIFO\fP policy, the following rules apply: -.IP * 3 +.IP 1) 3 A running \fBSCHED_FIFO\fP thread that has been preempted by another thread of higher priority will stay at the head of the list for its priority and will resume execution as soon as all threads of higher priority are blocked again. -.IP * +.IP 2) When a blocked \fBSCHED_FIFO\fP thread becomes runnable, it will be inserted at the end of the list for its priority. -.IP * +.IP 3) A call to .BR sched_setscheduler (2), .BR sched_setparam (2), @@ -179,7 +179,7 @@ it has the same priority. of the list.) .\" In 2.2.x and 2.4.x, the thread is placed at the front of the queue .\" In 2.0.x, the Right Thing happened: the thread went to the back -- MTK -.IP * +.IP 4) A thread calling .BR sched_yield (2) will be put at the end of the list.