projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
8b0b24c
)
Typographic fixes.
author
Ben Pfaff
<blp@cs.stanford.edu>
Fri, 31 Dec 2004 22:41:32 +0000
(22:41 +0000)
committer
Ben Pfaff
<blp@cs.stanford.edu>
Fri, 31 Dec 2004 22:41:32 +0000
(22:41 +0000)
doc/threads.texi
patch
|
blob
|
history
diff --git
a/doc/threads.texi
b/doc/threads.texi
index ac9ccd43cef23abedec89ab50b69e7fa1c79c258..af84ffea29fe22929240d075f60eb4a76b1830b7 100644
(file)
--- a/
doc/threads.texi
+++ b/
doc/threads.texi
@@
-429,8
+429,8
@@
Incidentally, we don't use @code{struct thread *} as
@func{thread_join}'s parameter type because a thread pointer is not
unique over time. That is, when a thread dies, its memory may be,
whether immediately or much later, reused for another thread. If
@func{thread_join}'s parameter type because a thread pointer is not
unique over time. That is, when a thread dies, its memory may be,
whether immediately or much later, reused for another thread. If
-thread
A over time had two children B and C that were stored at the
-same address, then @code{thread_join(@var{B})} and
+thread
@var{A} over time had two children @var{B} and @var{C} that
+
were stored at the
same address, then @code{thread_join(@var{B})} and
@code{thread_join(@var{C})} would be ambiguous. Introducing a thread
id or @dfn{tid}, represented by type @code{tid_t}, that is
intentionally unique over time solves the problem. The provided code
@code{thread_join(@var{C})} would be ambiguous. Introducing a thread
id or @dfn{tid}, represented by type @code{tid_t}, that is
intentionally unique over time solves the problem. The provided code