Seti@Home optimized science apps and information
Optimized Seti@Home apps => Linux => Topic started by: sunu on 21 Mar 2010, 05:11:20 pm
-
As the fermi release nears, just a heads up for those that will get the new cards.
Quoting nvidia's "Fermi Compatibility Guide" available from http://developer.nvidia.com/object/gpucomputing.html :
My application uses the CUDA Runtime API with CUDA Toolkit 2.1, 2.2, or 2.3.
How can I confirm that my application is ready to run on Fermi?
Answer: CUDA applications built using the CUDA Toolkit versions 2.1 through
2.3 are compatible with Fermi as long as they are built to include PTX versions of
their kernels. NVIDIA Driver versions 195.xx or newer allow the application to use
the PTX JIT code path. To test that PTX JIT is working for your application, you
can do the following:
- Go to the NVIDIA website, and install the latest R195 driver.
- Set the system environment flag CUDA_FORCE_PTX_JIT=1
- Launch your application.
When starting a CUDA application for the first time with the above environment
flag, the CUDA driver will JIT compile the PTX for each CUDA kernel that is used
into native CUBIN code. The generated CUBIN for the target GPU architecture is
cached by the CUDA driver. This cache persists across system shutdown/restart
events.
If this test passes, then your application is ready for Fermi.
Well, I got the new cuda 3.0 toolkit and did the following runs with my 9600GT:
No CUDA_FORCE_PTX_JIT flag:
cuda 2 OK
cuda 3 OK
CUDA_FORCE_PTX_JIT flag enabled:
cuda 2 OK
cuda 3 FAIL
What does this tell us? My estimate is that fermi will run the linux client at least with the 2.x libraries. Cuda 3 + ENV flag might be reserved only for fermi hardware, probably that's why it failed on my 9600GT.
-
Did you do some benchmarks already?
If driver can cache native binary for GPU, it could save some time on startup...
-
Unfortunately I didn't think of that beforehand and didn't keep time. Maybe one of these days I'll do a rerun.
-
so cufft can be connected to the specified stream ....