On Tue Dec 29 12:11:24 PST 2009 Jon Sonntag wrote:
>I've got a CUDA app working for OS X.  It is built with CUDA 2.2 (32-bit).
>It runs OK in standalone mode, so the next step is getting BOINC to
>acknowledge that a CUDA device exists so it can be tested within BOINC
>itself.  Unfortunately, I don't have a MAC with a CUDA card so the BOINC
>client reports that it found the NVIDIA drivers but no usable GPUs.  No
>surprise there.  There are drivers for both CUDA 2.2 (32 bit) and CUDA 2.3
>(32 and 64 bit).  Has anyone has gotten BOINC to recognize their CUDA card
>as a coprocessor?

I have posted the 6.10.26 release of BOINC for Macintosh for testing. 
This is a Mac-only release whose primary purpose is to implement CUDA 
capability on the Mac.  You can download it from 
<http://boinc.berkeley.edu/download_all.php>.

Previous versions of BOINC included a client in the form of a 
universal binary containing 3 architectures: PowerPC, Intel 32-bit 
and Intel 64-bit.  The Mac OS automatically chose the best one for 
each system. 

Unfortunately, the CUDA libraries have not worked with 64-bit 
applications yet.  So we eliminated the 64-bit client; the universal 
binary now contains only the PowerPC and Intel 32-bit architectures. 
This allows us to link with the CUDA libraries on Intel Macs.  The 
Intel 32-bit client determines at run time whether the Mac is 64-bit 
capable; if so, it requests 64-bit project applications (in addition 
to 32-bit project applications.) 

The only other side effect of this change is that the benchmarks had 
been run using 64-bit Intel instructions when available; now they 
will always use 32-bit instructions.  But the difference is small. 
And most project applications are 32-bit, so the 32-bit benchmarks 
are probably a more accurate estimate of performance.

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to