Browse Source

doc: extra comments

Nathalie Furmento 15 years ago
parent
commit
860ed32dc4
1 changed files with 10 additions and 0 deletions
  1. 10 0
      doc/starpu.texi

+ 10 - 0
doc/starpu.texi

@@ -1557,6 +1557,10 @@ to that vector made by other tasks.
 Contrary to the previous examples, the task submitted in this example may not
 Contrary to the previous examples, the task submitted in this example may not
 only be executed by the CPUs, but also by a CUDA device.
 only be executed by the CPUs, but also by a CUDA device.
 
 
+The CUDA implementation can be written as follows. It needs to be
+compiled with a CUDA compiler such as nvcc, the NVIDIA CUDA compiler
+driver.
+
 @example
 @example
 #include <starpu.h>
 #include <starpu.h>
 
 
@@ -1576,6 +1580,7 @@ extern "C" void cuda_codelet(void *descr[], void *_args)
 @}
 @}
 @end example
 @end example
 
 
+The CPU implementation can be as follows.
 @example
 @example
 #include <starpu.h>
 #include <starpu.h>
 
 
@@ -1590,6 +1595,11 @@ void cpu_codelet(void *descr[], void *_args)
 @}
 @}
 @end example
 @end example
 
 
+Here the source of the application. You can notice the value of the
+field @code{where} for the codelet. We specify
+@code{STARPU_CPU|STARPU_CUDA} to indicate to StarPU that the codelet
+can be executed either on a CPU or on a CUDA device.
+
 @example
 @example
 #include <starpu.h>
 #include <starpu.h>