projects
/
pintos-anon
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Add summary of scheduler.
[pintos-anon]
/
doc
/
threads.texi
diff --git
a/doc/threads.texi
b/doc/threads.texi
index 28b87fadaca14d2e2a5f61c76cf9c1b6883c40ff..6b93dbb0badbdd7cab26cb02e6ecee2826248167 100644
(file)
--- a/
doc/threads.texi
+++ b/
doc/threads.texi
@@
-328,9
+328,14
@@
timer ticks or input events. Turning off interrupts also increases the
interrupt handling latency, which can make a machine feel sluggish if
taken too far.
interrupt handling latency, which can make a machine feel sluggish if
taken too far.
+You may need to add or modify code where interrupts are already
+disabled, such as in @func{sema_up} or @func{sema_down}. You should
+still try to keep this code as short as you can.
+
Disabling interrupts can be useful for debugging, if you want to make
sure that a section of code is not interrupted. You should remove
Disabling interrupts can be useful for debugging, if you want to make
sure that a section of code is not interrupted. You should remove
-debugging code before turning in your project.
+debugging code before turning in your project. (Don't just comment it
+out, because that can make the code difficult to read.)
There should be no busy waiting in your submission. A tight loop that
calls @func{thread_yield} is one form of busy waiting.
There should be no busy waiting in your submission. A tight loop that
calls @func{thread_yield} is one form of busy waiting.