Hello, here are some questions I have
Is it possible to split a computation in multiple executables using the runtime api?
i.e., one executable loads data to the device, the next one performs some computation, …, and so on.
I tried this, but could not get it to work right.
So, I switched to driver api - and using this approach I have no problems. But the runtime api is a lot nicer to work with.
Is there a nice way to give the name of the kernel to cuModuleGetFunction() if the kernel is an instance of a template?
What should be specified in cuFuncSetSharedSize()? This is discussed here http://forums.nvidia.com/index.php?showtopic=68192
The (threadMigration, matrixMulDrv) sdk-examples seem to specify the size of the (in the examples statically) allocated smem for the kernel, but not for the kernel parameters (which also resides in the smem if I’m not mistaken).
When launching a kernel with only 32 threads per block, why does each thread allocate twice the registers needed?
This is what happens according to the occupancy calculator; in register allocations per block, the formula in the spreadsheet is written as:
The values from the occupancy calculator the same as measured with the visual profiler.
Why do things work like this? Will future devices also work in the same manner? (Or maybe itâ€™s not tied to workings in the hardware - maybe it will change in the next driver release? :-)
Have anyone been able to use the visual profiler for timing kernels run by mex files in matlab under windows? I have tried but failed. Iâ€™m using win xp pro, matlab 2007b, and have tried many versions of the visual profiler (newest being 1.0.11).
I have tried the method described here:
but I canâ€™t get it to work.
If I for example try to profile the script speed_fft.m (which comes in the matlab plug-in
http://developer.nvidia.com/object/matlab_cuda.html) I get: “Error -97 in reading profiler output. Unable to open file”.
The profiler creates some .cvs files which all contain the error message “Failed to open profile config file.”.
The error is reported before the matlab script has even started, after that the script is run.
(for all other matlab scripts I’ve tried to run I get the same error)