From 17102846d22591590c37548f8514067e2be6c5f6 Mon Sep 17 00:00:00 2001 From: Godmar Back Date: Wed, 13 Sep 2006 11:40:40 +0000 Subject: [PATCH] fixed left-over, now-wrong comment about how decrease in numeric priority means increase in effective priority --- doc/44bsd.texi | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/doc/44bsd.texi b/doc/44bsd.texi index d49f234..ba67dda 100644 --- a/doc/44bsd.texi +++ b/doc/44bsd.texi @@ -76,11 +76,10 @@ Thread priority is dynamically determined by the scheduler using a formula given below. However, each thread also has an integer @dfn{nice} value that determines how ``nice'' the thread should be to other threads. A @var{nice} of zero does not affect thread priority. A -positive @var{nice}, to the maximum of 20, increases the numeric -priority of a thread, decreasing its effective priority, and causes it -to give up some CPU time it would otherwise receive. On the other hand, -a negative @var{nice}, to the minimum of -20, tends to take away CPU -time from other threads. +positive @var{nice}, to the maximum of 20, decreases the priority of a +thread and causes it to give up some CPU time it would otherwise receive. +On the other hand, a negative @var{nice}, to the minimum of -20, tends +to take away CPU time from other threads. The initial thread starts with a @var{nice} value of zero. Other threads start with a @var{nice} value inherited from their parent -- 2.30.2