I seem to have a strange problem, when I run my program it works fine for some sizes (I’m working on 3D data, i.e. volumes) but for others I get “invalid argument” when I try to run a “cudaMemcpy3D” from global memory to an array bound to a 3D texture. I don’t remember having these problems in CUDA 2.3. Does anyone know if something has changed for texture memory and cudaMemcpy3D from CUDA 2.3 to 3.0 ?
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
cudaMemcpy3D Incorrect returned values | 0 | 1549 | February 3, 2009 | |
Copying to a 3D cuda array cudaMemcpyToArray returns cudaErrorInvalidValue | 4 | 17819 | June 9, 2010 | |
bug in cudaMemcpy3D bound checking? | 3 | 12238 | October 9, 2008 | |
3D texture problem | 3 | 4858 | January 8, 2011 | |
Undocumented function | 2 | 3449 | August 21, 2008 | |
problem with cudaMemcpy3D from device to cudaArray test code attached | 0 | 2457 | June 22, 2009 | |
Problem with cudaMemcpy3D Copy resoure to 3D Texture | 1 | 830 | June 25, 2011 | |
cudamemcpy3d issue | 1 | 582 | October 25, 2010 | |
CUDA graph 3D Memcpy update problem | 2 | 401 | August 8, 2023 | |
Problem to use the pitch, returned by cudaMallocPitch, with cudaMemcpy3D! | 0 | 2051 | February 20, 2009 |