projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
e647de5
)
Clarify that scheduler data updates are synchronous with the timer.
author
Ben Pfaff
<blp@cs.stanford.edu>
Mon, 27 Jun 2005 19:58:08 +0000
(19:58 +0000)
committer
Ben Pfaff
<blp@cs.stanford.edu>
Mon, 27 Jun 2005 19:58:08 +0000
(19:58 +0000)
doc/44bsd.texi
patch
|
blob
|
history
diff --git
a/doc/44bsd.texi
b/doc/44bsd.texi
index 4d61c17afb995b8daf753c6a57ad42f4d1419bf8..612aa1c74c51921168a319c2866e2a6b622b5466 100644
(file)
--- a/
doc/44bsd.texi
+++ b/
doc/44bsd.texi
@@
-52,6
+52,12
@@
time, the scheduler chooses a thread from the highest-priority non-empty
queue. If the highest-priority queue contains multiple threads, then
they run in ``round robin'' order.
queue. If the highest-priority queue contains multiple threads, then
they run in ``round robin'' order.
+Multiple facets of the scheduler require data to be updated after a
+certain number of timer ticks. In every case, these updates should
+occur before any ordinary kernel thread has a chance to run, so that
+there is no chance that a kernel thread could see @func{timer_ticks}
+increased but these old values for these data.
+
@menu
* Thread Niceness::
* Calculating Priority::
@menu
* Thread Niceness::
* Calculating Priority::