From: Ben Pfaff <blp@cs.stanford.edu>
Date: Sat, 25 Jun 2005 03:37:32 +0000 (+0000)
Subject: Be specific about `nice' range.
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c56ee34418c56190fe1cc2f2e22a5f8b34057cb7;p=pintos-anon

Be specific about `nice' range.
---

diff --git a/doc/44bsd.texi b/doc/44bsd.texi
index 84ddf7f..b99f3ca 100644
--- a/doc/44bsd.texi
+++ b/doc/44bsd.texi
@@ -64,13 +64,14 @@ they run in ``round robin'' order.
 @section Niceness
 
 Thread priority is dynamically determined by the scheduler using a
-formula given below.  However, each thread also has a relatively static
-@dfn{nice} value between -20 and 20 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} 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} tends to take away CPU time from other threads.
+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.
 
 The initial thread starts with a @var{nice} value of zero.  Other
 threads start with a @var{nice} value inherited from their parent