From: Ben Pfaff <blp@cs.stanford.edu>
Date: Wed, 7 Mar 2007 14:52:06 +0000 (+0000)
Subject: Fix inconstiency in recent_cpu update description.
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?p=pintos-anon;a=commitdiff_plain;h=a4a330725f78a769e6592edffdf5627e8d1d7623

Fix inconstiency in recent_cpu update description.
---

diff --git a/doc/44bsd.texi b/doc/44bsd.texi
index d27343f..e8ae113 100644
--- a/doc/44bsd.texi
+++ b/doc/44bsd.texi
@@ -182,7 +182,7 @@ current value of @var{recent_cpu} decays to a weight of .1 in
 received ``recently,'' with the rate of decay inversely proportional to
 the number of threads competing for the CPU.
 
-Assumptions made by some of the tests require that updates to
+Assumptions made by some of the tests require that these recalculations of
 @var{recent_cpu} be made exactly when the system tick counter reaches a
 multiple of a second, that is, when @code{timer_ticks () % TIMER_FREQ ==
 0}, and not at any other time.