Context Navigation

-                      r07c1e595
+                      r9f10d1f2
 \section{\protect\CFA 's Thread Building Blocks}
 One of the important features that is missing in C is threading. On modern architectures, a lack of threading is unacceptable\cite{Sutter05, Sutter05b}, and therefore modern programming languages must have the proper tools to allow users to write performant concurrent programs to take advantage of parallelism. As an extension of C, \CFA needs to express these concepts in a way that is as natural as possible to programmers familiar with imperative languages. And being a system-level language means programmers expect to choose precisely which features they need and which cost they are willing to pay.
+One of the important features that is missing in C is threading. On modern architectures, a lack of threading is unacceptable~\cite{Sutter05, Sutter05b}, and therefore modern programming languages must have the proper tools to allow users to write performant concurrent programs to take advantage of parallelism. As an extension of C, \CFA needs to express these concepts in a way that is as natural as possible to programmers familiar with imperative languages. And being a system-level language means programmers expect to choose precisely which features they need and which cost they are willing to pay.
 \section{Coroutines: A stepping stone}\label{coroutine}
 …
 void fibonacci_array(
         int n,
         int * array
+        int* array
 ) {
         int f1 = 0; int f2 = 1;
 …
 int fibonacci_state(
         Iterator_t * it
+        Iterator_t* it
 ) {
         int f;
 …
 A good example of a problem made easier with coroutines is generators, like the Fibonacci sequence. This problem comes with the challenge of decoupling how a sequence is generated and how it is used. Figure \ref{lst:fibonacci-c} shows conventional approaches to writing generators in C. All three of these approach suffer from strong coupling. The left and center approaches require that the generator have knowledge of how the sequence is used, while the rightmost approach requires holding internal state between calls on behalf of the generator and makes it much harder to handle corner cases like the Fibonacci seed.
 Figure \ref{lst:fibonacci-cfa} is an example of a solution to the Fibonacci problem using \CFA coroutines, where the coroutine stack holds sufficient state for the generation. This solution has the advantage of having very strong decoupling between how the sequence is generated and how it is used. Indeed, this version is as easy to use as the \code{fibonacci_state} solution, while the implementation is very similar to the \code{fibonacci_func} example.
+Figure \ref{lst:fibonacci-cfa} is an example of a solution to the Fibonacci problem using \CFA coroutines, where the coroutine stack holds sufficient state for the next generation. This solution has the advantage of having very strong decoupling between how the sequence is generated and how it is used. Indeed, this version is as easy to use as the \code{fibonacci_state} solution, while the implementation is very similar to the \code{fibonacci_func} example.
 \begin{figure}
 …
 };
 void ?{}(Fibonacci & this) { //constructor
+void ?{}(Fibonacci& this) { //constructor
         this.fn = 0;
+}
 //main automatically called on first resume
 void main(Fibonacci & this) with (this) {
+void main(Fibonacci& this) with (this) {
         int fn1, fn2;           //retained between resumes
         fn  = 0;
 …
+}
 int next(Fibonacci & this) {
+int next(Fibonacci& this) {
         resume(this); //transfer to last suspend
         return this.fn;
 …
 \end{figure}
 Figure \ref{lst:fmt-line} shows the \code{Format} coroutine which rearranges text in order to group characters into blocks of fixed size. The example takes advantage of resuming coroutines in the constructor to simplify the code and highlights the idea that interesting control flow can occur in the constructor.
+Figure \ref{lst:fmt-line} shows the \code{Format} coroutine for restructuring text into groups of character blocks of fixed size. The example takes advantage of resuming coroutines in the constructor to simplify the code and highlights the idea that interesting control flow can occur in the constructor.
 \begin{figure}
 …
 };
 void  ?{}(Format & fmt) {
+void  ?{}(Format& fmt) {
         resume( fmt );                                                  //prime (start) coroutine
+}
 void ^?{}(Format & fmt) with fmt {
+void ^?{}(Format& fmt) with fmt {
         if ( fmt.g != 0 || fmt.b != 0 )
         sout | endl;
+}
 void main(Format & fmt) with fmt {
+void main(Format& fmt) with fmt {
         for ( ;; ) {                                                    //for as many characters
                 for(g = 0; g < 5; g++) {                //groups of 5 blocks
 …
 \subsection{Construction}
 One important design challenge for coroutines and threads (shown in section \ref{threads}) is that the runtime system needs to run code after the user-constructor runs to connect the fully constructed object into the system. In the case of coroutines, this challenge is simpler since there is no non-determinism from preemption or scheduling. However, the underlying challenge remains the same for coroutines and threads.
 The runtime system needs to create the coroutine's stack and more importantly prepare it for the first resumption. The timing of the creation is non-trivial since users both expect to have fully constructed objects once execution enters the coroutine main and to be able to resume the coroutine from the constructor. As regular objects, constructors can leak coroutines before they are ready. There are several solutions to this problem but the chosen options effectively forces the design of the coroutine.
+One important design challenge for implementing coroutines and threads (shown in section \ref{threads}) is that the runtime system needs to run code after the user-constructor runs to connect the fully constructed object into the system. In the case of coroutines, this challenge is simpler since there is no non-determinism from preemption or scheduling. However, the underlying challenge remains the same for coroutines and threads.
+The runtime system needs to create the coroutine's stack and more importantly prepare it for the first resumption. The timing of the creation is non-trivial since users both expect to have fully constructed objects once execution enters the coroutine main and to be able to resume the coroutine from the constructor. There are several solutions to this problem but the chosen options effectively forces the design of the coroutine.
 Furthermore, \CFA faces an extra challenge as polymorphic routines create invisible thunks when casted to non-polymorphic routines and these thunks have function scope. For example, the following code, while looking benign, can run into undefined behaviour because of thunks:
 …
 \begin{ccode}
 extern void async(/* omitted */, void (*func)(void *), void *obj);
 void noop(/* omitted */, void *obj){}
+extern void async(/* omitted */, void (*func)(void*), void* obj);
+void noop(/* omitted */, void* obj){}
 void bar(){
         int a;
         void _thunk0(int *_p0){
+        void _thunk0(int* _p0){
                 /* omitted */
                 noop(/* omitted */, _p0);
+        }
         /* omitted */
         async(/* omitted */, ((void (*)(void *))(&_thunk0)), (&a));
+        async(/* omitted */, ((void (*)(void*))(&_thunk0)), (&a));
+}
 \end{ccode}
 The problem in this example is a storage management issue, the function pointer \code{_thunk0} is only valid until the end of the block, which limits the viable solutions because storing the function pointer for too long causes undefined behavior; i.e., the stack-based thunk being destroyed before it can be used. This challenge is an extension of challenges that come with second-class routines. Indeed, GCC nested routines also have the limitation that nested routine cannot be passed outside of the declaration scope. The case of coroutines and threads is simply an extension of this problem to multiple call-stacks.
+The problem in this example is a storage management issue, the function pointer \code{_thunk0} is only valid until the end of the block, which limits the viable solutions because storing the function pointer for too long causes Undefined Behavior; i.e., the stack-based thunk being destroyed before it can be used. This challenge is an extension of challenges that come with second-class routines. Indeed, GCC nested routines also have the limitation that nested routine cannot be passed outside of the declaration scope. The case of coroutines and threads is simply an extension of this problem to multiple call-stacks.
 \subsection{Alternative: Composition}
 …
 };
 void FibMain(void *) {
+void FibMain(void*) {
         //...
+}
 void ?{}(Fibonacci & this) {
+void ?{}(Fibonacci& this) {
         this.fn = 0;
         //Call constructor to initialize coroutine
 …
+}
 \end{cfacode}
 The downside of this approach is that users need to correctly construct the coroutine handle before using it. Like any other objects, doing so the users carefully choose construction order to prevent usage of objects not yet constructed. However, in the case of coroutines, users must also pass to the coroutine information about the coroutine main, like in the previous example. This opens the door for user errors and requires extra runtime storage to pass at runtime information that can be known statically.
+The downside of this approach is that users need to correctly construct the coroutine handle before using it. Like any other objects, the user must carefully choose construction order to prevent usage of objects not yet constructed. However, in the case of coroutines, users must also pass to the coroutine information about the coroutine main, like in the previous example. This opens the door for user errors and requires extra runtime storage to pass at runtime information that can be known statically.
 \subsection{Alternative: Reserved keyword}
 …
 \subsection{Alternative: Lambda Objects}
 For coroutines as for threads, many implementations are based on routine pointers or function objects\cite{Butenhof97, ANSI14:C++, MS:VisualC++, BoostCoroutines15}. For example, Boost implements coroutines in terms of four functor object types:
+For coroutines as for threads, many implementations are based on routine pointers or function objects~\cite{Butenhof97, ANSI14:C++, MS:VisualC++, BoostCoroutines15}. For example, Boost implements coroutines in terms of four functor object types:
 \begin{cfacode}
 asymmetric_coroutine<>::pull_type
 …
 A variation of this would be to use a simple function pointer in the same way pthread does for threads :
 \begin{cfacode}
 void foo( coroutine_t cid, void * arg ) {
         int * value = (int *)arg;
+void foo( coroutine_t cid, void* arg ) {
+        int* value = (int*)arg;
         //Coroutine body
+}
 …
+}
 \end{cfacode}
 This semantics is more common for thread interfaces than coroutines works equally well. As discussed in section \ref{threads}, this approach is superseded by static approaches in terms of expressivity.
+This semantics is more common for thread interfaces but coroutines work equally well. As discussed in section \ref{threads}, this approach is superseded by static approaches in terms of expressivity.
 \subsection{Alternative: Trait-based coroutines}
 …
 \begin{cfacode}
 trait is_coroutine(dtype T) {
       void main(T & this);
       coroutine_desc * get_coroutine(T & this);
 };
 forall( dtype T | is_coroutine(T) ) void suspend(T &);
 forall( dtype T | is_coroutine(T) ) void resume (T &);
 \end{cfacode}
 This ensures an object is not a coroutine until \code{resume} is called on the object. Correspondingly, any object that is passed to \code{resume} is a coroutine since it must satisfy the \code{is_coroutine} trait to compile. The advantage of this approach is that users can easily create different types of coroutines, for example, changing the memory layout of a coroutine is trivial when implementing the \code{get_coroutine} routine. The \CFA keyword \code{coroutine} only has the effect of implementing the getter and forward declarations required for users to only have to implement the main routine.
+      void main(T& this);
+      coroutine_desc* get_coroutine(T& this);
+};
+forall( dtype T | is_coroutine(T) ) void suspend(T&);
+forall( dtype T | is_coroutine(T) ) void resume (T&);
+\end{cfacode}
+This ensures an object is not a coroutine until \code{resume} is called on the object. Correspondingly, any object that is passed to \code{resume} is a coroutine since it must satisfy the \code{is_coroutine} trait to compile. The advantage of this approach is that users can easily create different types of coroutines, for example, changing the memory layout of a coroutine is trivial when implementing the \code{get_coroutine} routine. The \CFA keyword \code{coroutine} only has the effect of implementing the getter and forward declarations required for users to implement the main routine.
 \begin{center}
 …
 static inline
 coroutine_desc * get_coroutine(
         struct MyCoroutine & this
+coroutine_desc* get_coroutine(
+        struct MyCoroutine& this
 ) {
         return &this.__cor;
+}
 void main(struct MyCoroutine * this);
+void main(struct MyCoroutine* this);
 \end{cfacode}
 \end{tabular}
 …
         this.func( this.arg );
+}
+void hello(/*unused*/ int) {
+        sout | "Hello World!" | endl;
+}
+int main() {
+        FuncRunner f = {hello, 42};
+        return 0'
+}
 \end{cfacode}
 …
 //main
 void main(MyThread & this) {
+void main(MyThread& this) {
         //...
+}
 …
 \end{cfacode}
 However, one of the drawbacks of this approach is that threads now always form a lattice, that is they are always destroyed in the opposite order of construction because of block structure. This restriction is relaxed by using dynamic allocation, so threads can outlive the scope in which they are created, much like dynamically allocating memory lets objects outlive the scope in which they are created.
+However, one of the drawbacks of this approach is that threads always form a lattice, i.e., they are always destroyed in the opposite order of construction because of block structure. This restriction is relaxed by using dynamic allocation, so threads can outlive the scope in which they are created, much like dynamically allocating memory lets objects outlive the scope in which they are created.
 \begin{cfacode}
 …
 };
 void main(MyThread & this) {
+void main(MyThread& this) {
         //...
+}
 void foo() {
         MyThread * long_lived;
+        MyThread* long_lived;
+        {
                 //Start a thread at the beginning of the scope

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 9f10d1f2 for doc/proposals/concurrency/text/basics.tex

Legend:

doc/proposals/concurrency/text/basics.tex

Download in other formats: