I am having trouble finding any examples of host to CUDA 2D array copying that show how the data is configured on the host side. Everyone shows the CUDA side but not host.
So My problem is that I am getting incorrect results when accessing my array bound to a texture. First I am defining my data on the host side as a 1D array of unsigned ints like so: (I apologize for the size of these boxes, I am not sure how to make them smaller)
[codebox]unsigned int m_data[INT_COUNT];[/codebox]
I then pass that through to my cuda code as an argument as:
void Cuda_Code(unsigned int* pVolumeData, int nNumVolData)
}[/codebox] (that isn’t the real code but you get the idea)
I have a texture defined in my cuda code like so:
[codebox]texture<uint, 2, cudaReadModeElementType> volumeDataDTex;[/codebox]
I then allocate the CUDA memory, copy my host memory over to the memory and then bind the texture to the array like so:
[codebox]cudaArray* volumeTexArray = 0;
cudaMallocArray(&volumeTexArray, &volumeDataDTex.channelDesc, INT_COUNT, nNumVolData);
cudaMemcpy2DToArray(volumeTexArray, 0, 0, pVolumeData, INT_COUNT * sizeof(uint), INT_COUNT * sizeof(uint), nNumVolData, cudaMemcpyHostToDevice);
When I access the data in my kernel I do it like so:
[codebox]uint sliceP = tex2D(volumeDataDTex, index, nStepcount);[/codebox]
I do not believe I am setting up the texture correctly because the data is wrong and I can verify the data is correct on the CPU side. My understanding of how the call cudaMemcpy2DToArray works is that I just need to give it source and destination buffers and then the pitch needs to be the size in bytes of the width of the data which is also the second argument (not sure why it has both) and the the number of rows in height. I am guessing that the pitch and the width in bytes is referring to the host side layout and the height is what I want the cuda array to have (it doesn’t apparently have that information from the cudaArray?).
What am I misunderstanding? it seems I should be getting good data here but I am not. The reference guide is a bit cryptic.