Changes between Version 25 and Version 26 of AppPlan

Timestamp:

Jun 6, 2012, 9:55:06 AM (12 years ago)

Author:

davea

Comment:

--

AppPlan

@@ -1 @@
-= Application planning =
+= Plan classes =
 
-'''Application planning''' is a mechanism that lets the scheduler decide,
+'''Plan classes''' is a mechanism that lets the scheduler decide,
 using project-supplied logic:
 
@@ -13 +13 @@
 See [AppVersionNew how to specify an app version's plan class].
 
-The scheduler is linked with a function
-{{{
-bool app_plan(SCHEDULER_REQUEST &sreq, char* plan_class, HOST_USAGE&);
-}}}
-The '''sreq''' argument describes the host.
-It contains:
- * in '''sreq.host''' field, a description of the host's hardware, including:
-  * In p_vendor and p_model, the processor type
-  * In p_features, the processor features (e.g., fpu tsc pae nx sse sse2 mmx)
-  * In m_nbytes, the amount of RAM
- * in '''sreq.coprocs''', a list of the hosts's coprocessors.
- * in '''core_client_version''', the client's version number in MMmmRR form.
-
-When called with a particular SCHEDULER_REQUEST and plan class,
-the function returns true if the host's resources are sufficient for apps of that class.
-If true, it populates the HOST_USAGE structure:
-{{{
-struct HOST_USAGE {
-   double ncudas;     // number of NVIDIA GPUs used
-   double natis;      // number of ATI GPUs used
-   double gpu_ram;    // max amount of GPU RAM used
-   double avg_ncpus;  // avg #CPUs used by app (may be fractional)
-   double max_ncpus;  // max #CPUs used (not currently used for anything)
-   double projected_flops;
-      // an estimate of the actual FLOPS.
-      // used to select versions, so make it higher for the preferred version
-   double peak_flops;
-      // the peak FLOPS of the devices to be used
-   char cmdline[256]; // passed to the app as a cmdline argument;
-                      // this can be used, e.g. to control the # of threads used
-};
-}}}
-
 When deciding whether to send a job to a host,
 the scheduler examines all latest-version app_versions for the platform,
@@ -54 +21 @@
 won't start the app unless that much RAM is available on the allocated GPU.
 
-You are free to define your own set of plan classes,
-and to link your own '''app_plan()''' function with the scheduler.
-The BOINC scheduler comes with a default '''app_plan()''' (in sched/sched_customize.cpp).
+
 This defines the following plan classes:
 
@@ -64 +29 @@
  '''vbox32''':: An app that runs in a 32-bit VirtualBox VM
  '''vbox64''':: An app that runs in a 64-bit VirtualBox VM
+Each coprocessor application has an associated [wiki:AppPlan plan class]
+which determines the hardware and software resources that are needed to run the application.
 
-... and a number of [AppCoprocessor GPU plan classes].
+'''NOTE: plan classes for AMD GPUs must contain the substring 'ati';
+plan classes for NVIDIA GPUs much contain either 'nvidia' or 'cuda' as a substring.'''
+
+The following plan classes for NVIDIA are pre-defined:
+
+ '''cuda''':: NVIDIA GPU, compute capability 1.0+, driver version 177.00+, 254+ MB RAM.
+ '''cuda23''':: Requires driver version 190.38+, 384+ MB RAM.
+ '''cuda_fermi''':: Requires compute capability 2.0+ and CUDA version 3.0+
+ '''opencl_nvidia_101''':: Requires OpenCL 1.1+ support
+
+For ATI the situation is more complex because AMD changed the DLL names from amd* to ati* midstream;
+applications are linked against a particular name and will fail if it's not present.
+
+ '''ati''':: CAL version 1.0.0+, amd* DLLs
+ '''ati13amd''':: CAL version 1.3+, amd* DLLs
+ '''ati13ati''':: CAL version 1.3+, ati* DLLs
+ '''ati14''':: CAL version 1.4+, ati* DLLs
+ '''opencl_ati_101''':: OpenCL 1.1+
+
+You can verify which DLLs your application is linked against by using
+[http://www.dependencywalker.com/ Dependency Walker] against your application.
+If your executable contains DLL names prefixed with 'amd' then your plan class
+will be ati or ati13amd depending on which version of the CAL SDK you are using.
+If the DLL names are prefixed with 'ati' then use the ati13ati or ati14 plan classes.
+
+In all cases (NVIDIA and ATI), the application is assumed to use 1 GPU,
+and the CPU usage is assumed to be 0.5% the FLOPS of the GPU.
+If there is a choice, the scheduler will give preference to later classes,
+i.e. it will pick cuda23 over cuda.
+
+Once you have chosen a plan class for your executable,
+create an [wiki:UpdateVersions app version], specifying its plan class.
+
 
 '''Note: plan classes containing the substrings 'nvidia', 'cuda', and 'ati' are reserved