projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
c9933c8
)
Priority change clarification (problem 1-3).
author
Ben Pfaff
<blp@cs.stanford.edu>
Fri, 14 Jan 2005 07:59:41 +0000
(07:59 +0000)
committer
Ben Pfaff
<blp@cs.stanford.edu>
Fri, 14 Jan 2005 07:59:41 +0000
(07:59 +0000)
doc/threads.texi
patch
|
blob
|
history
diff --git
a/doc/threads.texi
b/doc/threads.texi
index dae47bb908a2fb87430c114e39efe15246e00c1f..7d7526c908e055364ac40110bf8e6f8cfac58832 100644
(file)
--- a/
doc/threads.texi
+++ b/
doc/threads.texi
@@
-527,7
+527,9
@@
than the currently running thread, the current thread should
immediately yield the processor to the new thread. Similarly, when
threads are waiting for a lock, semaphore or condition variable, the
highest priority waiting thread should be woken up first. A thread
immediately yield the processor to the new thread. Similarly, when
threads are waiting for a lock, semaphore or condition variable, the
highest priority waiting thread should be woken up first. A thread
-may set its priority at any time.
+may raise or lower its own priority at any time, but lowering its
+priority such that it no longer has the highest priority must cause it
+to immediately yield the CPU.
One issue with priority scheduling is ``priority inversion'': if a
high priority thread needs to wait for a low priority thread (for
One issue with priority scheduling is ``priority inversion'': if a
high priority thread needs to wait for a low priority thread (for