Changeset cf966b5 for doc/proposals/concurrency/text/together.tex

Timestamp:

Nov 28, 2017, 3:52:01 PM (7 years ago)

Author:

Thierry Delisle <tdelisle@…>

Branches:

ADT, aaron-thesis, arm-eh, ast-experimental, cleanup-dtors, deferred_resn, demangler, enum, forall-pointer-decay, jacob/cs343-translation, jenkins-sandbox, master, new-ast, new-ast-unique-expr, new-env, no_list, persistent-indexer, pthread-emulation, qualifiedEnum, resolv-new, with_gc

Children:

6c2ba38

Parents:

f7a4f89

Message:

Results need to be updated but otherwise, tentative final draft

File:

• doc/proposals/concurrency/text/together.tex (modified) (4 diffs)

doc/proposals/concurrency/text/together.tex

@@ -7 +7 @@
 
 \section{Threads as monitors}
-As it was subtly alluded in section \ref{threads}, \code{threads} in \CFA are in fact monitors, which means that all monitor features are available when using threads. For example, here is a very simple two thread pipeline that could be used for a simulator of a game engine :
-\begin{cfacode}
+As it was subtly alluded in section \ref{threads}, \code{thread}s in \CFA are in fact monitors, which means that all monitor features are available when using threads. For example, here is a very simple two thread pipeline that could be used for a simulator of a game engine :
+\begin{figure}[H]
+\begin{cfacode}[caption={Toy simulator using \code{thread}s and \code{monitor}s.},label={lst:engine-v1}]
 // Visualization declaration
 thread Renderer {} renderer;
@@ -36 +37 @@
 }
 \end{cfacode}
+\end{figure}
 One of the obvious complaints of the previous code snippet (other than its toy-like simplicity) is that it does not handle exit conditions and just goes on forever. Luckily, the monitor semantics can also be used to clearly enforce a shutdown order in a concise manner :
-\begin{cfacode}
+\begin{figure}[H]
+\begin{cfacode}[caption={Same toy simulator with proper termination condition.},label={lst:engine-v2}]
 // Visualization declaration
 thread Renderer {} renderer;
@@ -76 +79 @@
 // Call destructor for renderer to signify shutdown
 \end{cfacode}
+\end{figure}
 
 \section{Fibers \& Threads}
@@ -84 +88 @@
 }
 \end{cfacode}
-This function is called by the kernel to fetch the default preemption rate, where 0 signifies an infinite time-slice i.e. no preemption. However, once clusters are fully implemented, it will be possible to create fibers and uthreads in on the same system :
+This function is called by the kernel to fetch the default preemption rate, where 0 signifies an infinite time-slice, i.e., no preemption. However, once clusters are fully implemented, it will be possible to create fibers and \glspl{uthread} in the same system, as in listing \ref{lst:fiber-uthread}
 \begin{figure}
-\begin{cfacode}
+\begin{cfacode}[caption={Using fibers and \glspl{uthread} side-by-side in \CFA},label={lst:fiber-uthread}]
 //Cluster forward declaration
 struct cluster;