That's good news. I'm planning on making all the next Collatz CPU applications OpenCL based, so AMD, NVIDIA and Intel covers Windows and Linux. I'm guessing that in order to make OS X work the same way that the BOINC client reports the device vendor instead of the platform name and platform vendor since both of those would be "Apple" and make it difficult to keep the CUDA vs OpenCL indexing in sync.
On Wed, Jan 29, 2014 at 5:05 PM, David Anderson <da...@ssl.berkeley.edu>wrote: > Jon: > > The current BOINC client checks for all OpenCL/CPU drivers > (currently Intel, AMD, and NVIDIA; > any combination of these may exist on a given machine). > > It reports these to the server in an array called > host.host_info.opencl_cpu_prop[]; the number of entries is > host.host_info.num_opencl_cpu_platforms. > A plan class function can look at this array and see if the driver > it needs is available. > > It looks like we forgot to document this; I'll try to fix this soon. > > -- David > > > On 29-Jan-2014 10:41 AM, Jon Sonntag wrote: > > That brings up another question though... >> What's with the "opencl_cpu_intel" plan class name? Is Dr. Rodney McKay >> on >> the Berkeley payroll again? ;-) If the current plan class is >> "opencl_intel_gpu" shouldn't the CPU version be named "opencl_intel_cpu" ? >> Or better yet, to be consistent with the other coproc names, shouldn't >> they >> be "opencl_intel_cpu_102" and "opencl_intel_gpu_102" since Intel's current >> version (Intel SDK for OpenCL Applications XE 2013 R3) uses OpenCL 1.2 >> drivers? >> >> Is OpenCL CPU support limited to Intel? I ask because Intel's only >> current >> version for Linux is aimed at Xeons and won't even run on Core 2s, I7s, >> etc. whereas the AMD version works on AMD CPUs as well as non-Xeon and >> older SSE2 CPUs. AMD's version also runs within a virtual machine when >> using the CPU, at least with Win 8.1 host and an Ubuntu virtual machine. >> If AMD support won't be added for a while, I'll go ahead and make my CPU >> apps work with both AMD and Intel and try using AMD first if the processor >> is not a Xeon. >> >> Finally, even though clinfo runs successfully on Linux when using the >> Intel >> SDK for OpenCL Applications XE 2013 R3 runtime/SDK, clinfo doesn't >> actually >> create a context and when that is attempted, one gets a device not >> available error unless using a supported CPU. So, clinfo may work but >> hello world will not. You can compile with the Intel lib and run using >> the >> AMD platform though. >> >> Jon Sonntag >> _______________________________________________ >> boinc_dev mailing list >> boinc_dev@ssl.berkeley.edu >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. >> >> _______________________________________________ > boinc_dev mailing list > boinc_dev@ssl.berkeley.edu > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
