Explorar o código

confirm that non-parallel tasks can still run concurrently even with single combined worker

Samuel Thibault %!s(int64=12) %!d(string=hai) anos
pai
achega
91e20165f2
Modificáronse 2 ficheiros con 4 adicións e 2 borrados
  1. 2 1
      doc/chapters/advanced-examples.texi
  2. 2 1
      doc/chapters/basic-api.texi

+ 2 - 1
doc/chapters/advanced-examples.texi

@@ -923,7 +923,8 @@ sections for instance.
 The solution is then to use only one combined worker at a time.  This can be
 done by setting @code{single_combined_worker} to 1 in the @code{starpu_conf}
 structure, or setting the @code{STARPU_SINGLE_COMBINED_WORKER} environment
-variable to 1. StarPU will then run only one parallel task at a time.
+variable to 1. StarPU will then run only one parallel task at a time (but other
+CPU and GPU tasks are not affected and can be run concurrently)
 
 @node Debugging
 @section Debugging

+ 2 - 1
doc/chapters/basic-api.texi

@@ -138,7 +138,8 @@ to @code{-1}, the default value is used.  This can also be specified with the
 By default, StarPU executes parallel tasks concurrently.
 Some parallel libraries (e.g. most OpenMP implementations) however do
 not support concurrent calls to parallel code. In such case, setting this flag
-makes StarPU only start one parallel task at a time.
+makes StarPU only start one parallel task at a time (but other
+CPU and GPU tasks are not affected and can be run concurrently).
 This can also be specified with the @code{STARPU_SINGLE_COMBINED_WORKER} environment variable.
 
 @item @code{int disable_asynchronous_copy} (default = 0)