search for: clsvmalloc

...to the GPU? > > Jason I agree it is somewhat weird. The OpenCL 2.2 specification says that clEnqueueSVMMigrateMem() takes an array of pointers and sizes (in bytes) but the size is optional. There is no alignment required. This "works" because the pointers have to be allocated with clSVMAlloc() and presumably, the implementation for clSVMAlloc() keeps track of the length allocated and can fill that in if size is zero. However, requiring all allocations to be made with clSVMAlloc() defeats the goal of being able to use regular malloc() and mmap() allocations for OpenCL implementations th...

...son > > I agree it is somewhat weird. The OpenCL 2.2 specification says that > clEnqueueSVMMigrateMem() takes an array of pointers and sizes (in bytes) > but the size is optional. There is no alignment required. > This "works" because the pointers have to be allocated with clSVMAlloc() > and presumably, the implementation for clSVMAlloc() > keeps track of the length allocated and can fill that in if size is zero. > However, requiring all allocations to be made with clSVMAlloc() defeats the > goal of being able to use regular malloc() and mmap() allocations for OpenC...

The user level OpenCL code shouldn't have to align start and end addresses to a page boundary. That is better handled in the nouveau driver. The npages field is also redundant since it can be computed from the start and end addresses. Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> --- This is for Ben Skegg's nouveau tree. I have been working with Karol Herbst on the