Question

I'm trying to profile a kernel that uses 3D surfaces to read and write to 3D cudaArrays.

Unfortunately nvprof shows absolutely nothing for any texture reads or writes or cache activity etc.

It is also showing very poor memory access etc.

The application works perfectly so the surface read and write calls are obviously working.

Any ideas on this? Perhaps nvprof cant show surface activity yet?

Was it helpful?

Solution

NVIDA profilers do not currently supported analysis of surface or texture accesses.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top