Changes between Version 41 and Version 42 of AppCoprocessor

Timestamp:

Jul 8, 2013, 2:45:41 PM (11 years ago)

Author:

davea

Comment:

--

AppCoprocessor

@@ -2 +2 @@
 = Applications that use coprocessors =
 BOINC supports applications that use coprocessors.
-The supported coprocessor types (as of [24404])are NVIDIA and ATI GPUs.
+The supported coprocessor types are NVIDIA, AMD, and Intel GPUs.
 
 The BOINC client probes for coprocessors and reports them in scheduler requests.
-The client keeps track of coprocessor allocation, i.e. how many instances of each are free.
-It only runs an app if enough instances are available.
+The client keeps track of coprocessor allocation, i.e. which instances of each are free.
+When it turns a GPU app, it assigns it to a free instance.
 
 You can develop your application using any programming system,
@@ -21 +21 @@
 boinc_temporary_exit(60);
 }}}
-This will exit the application, and will tell the BOINC client to restart
+This exits the application and tells the BOINC client to restart
 it again in at least 60 seconds,
 at which point memory may be available.
@@ -50 +50 @@
 }}}
 
-== Cleanup on premature exit ==
+== Do GPU kernels within critical sections ==
 
 The BOINC client may kill your application during execution.
-This may leave the GPU in a bad state.
-To prevent this, call
+If a GPU kernel is in progress at this point, a system crash or hang may occur.
+To prevent this, do GPU kernels within a critical section, e.g.
 
 {{{
 boinc_begin_critical_section();
-}}}
-before using the GPU, and between GPU kernels do
-
-{{{
-if (boinc_status.quit_request || boinc_status.abort_request) {
-    // cudaThreadSynchronize(); or whatever is needed
-    boinc_end_critical_section();
-    exit(0);
-}
+... do GPU kernel
+boinc_end_critical_section();
 }}}