Changes between Version 5 and Version 6 of AppCoprocessor

Timestamp:

Mar 12, 2008, 11:16:21 AM (17 years ago)

Author:

davea

Comment:

--

AppCoprocessor

@@ -3 +3 @@
 This document describes BOINC's support for applications that use coprocessors such as
 
- * GPU(s)
- * SPEs in a Cell processor
+ * GPUs
+ * Cell SPEs
 
-We'll assume that these resources are "allocated" rather than "scheduled":
-an application using a coprocessor has it locked
-while the app is in memory,
+We'll assume that these resources are allocated rather than scheduled:
+i.e., an application using a coprocessor has it locked while the app is in memory,
 even if the app is suspended by BOINC or descheduled by the OS.
 
 == Proposed design ==
 
- 1. The BOINC client will probe for coprocessors, and report them in scheduler requests.  The XML looks like:
+The BOINC client probes for coprocessors and reports them in scheduler requests.
+The XML looks like:
 {{{
 <coprocs>
@@ -24 +24 @@
 </coprocs>
 }}}
- 1. An app_version record (in the server DB) will have a new field '''coproc_req''', which is a character string encoding its coprocessor requirements.
- 1. The scheduler is linked with a project-specific function
+ 1. An app_version record (in the server DB) has a character string field '''class'''.
+ 1. The scheduler is linked with a project-supplied function
 {{{
-bool coprocessor_compatible(COPROCS&, char coproc_req, double& flops);
+bool analyze_app(HOST&, char* class, double& flops);
 }}}
 This function: