Changes between Version 31 and Version 32 of AppPlan

Timestamp:

May 15, 2018, 4:56:31 PM (7 years ago)

Author:

davea

Comment:

--

AppPlan

@@ -21 +21 @@
  * by [PlanClassFunc expressing the policy in C++ code].
 
+== Plan class names ==
+
+Plan class names encode information as follows:
+
+ * The name includes "opencl" if and only if the app requires OpenCL libraries.
+ * The name includes "cuda" if and only if the app requires CUDA libraries.
+ * The name includes "ati" if and only if the app requires CAL libraries.
+ * The name includes "ati" or "amd" if and only if the app uses an ATI/AMD GPU.
+ * The name includes "cuda" or "nvidia" if and only if the app uses an NVIDIA GPU
+ * The name includes "intel_gpu" if and only if the app uses an Intel GPU.
+ * The name includes "vbox" if and only if the app is a VM app and requires VirtualBox.
+
+This is a bit ugly, but plan class names are interpreted according to these rules
+in both the client and the PHP code, so we can't change this for now.
+
 == Predefined plan classes ==
 
@@ -34 +49 @@
 
 === GPU plan classes ===
-
-Note: plan classes containing the substrings 'nvidia', 'cuda', 'amd' and 'ati' are reserved
-for GPU applications.
-Plan classes for AMD GPUs must contain the substring 'ati' or 'amd';
-plan classes for NVIDIA GPUs much contain either 'nvidia' or 'cuda' as a substring;
-plan classes for OpenCL applications must include 'opencl' as a substring.
 
 The following plan classes for NVIDIA are pre-defined:
@@ -55 +64 @@
  '''ati13ati''':: CAL version 1.3+, ati* DLLs
  '''ati14''':: CAL version 1.4+, ati* DLLs
- '''opencl_ati_101''':: OpenCL 1.1+
+ '''opencl_amd_101''':: OpenCL 1.1+
 
 You can verify which DLLs your application is linked against by using