cuda.core 1.4.0 Release Notes#

Fixes and enhancements#

  • Kernels, Buffer.fill() and asynchronous copies now work on PinnedMemoryResource buffers on every device that supports the pool’s kind of host memory pool, as on cudaMallocHost memory. In cuda.core 1.3.0, only the device that was current when the resource was created could access its buffers. A process that imported the pool, through PinnedMemoryResource.from_allocation_handle() or by unpickling, granted no device access at all, because pool access is per process. There, kernels failed with CUDA_ERROR_ILLEGAL_ADDRESS, fill failed with CUDA_ERROR_INVALID_VALUE, and copies silently blocked the host until earlier work on the stream completed. The creating and the importing process now both grant read and write access to every supporting device. (#3415, #3501)

  • Repeat imports of a memory pool in one process, for example passing a raw file descriptor to PinnedMemoryResource.from_allocation_handle() twice, now share one owner, which releases the pool with the last of them. Closing one import no longer removes device access to a pinned pool from the others, or emits a CUDAWarning from cuMemPoolDestroy for a device pool while a buffer imported through another is alive. An import that overlaps the release of the last one waits for it, and concurrent imports of one allocation handle return the same resource instead of raising an internal error. (#3510)

  • DeviceMemoryResource.from_allocation_handle() returns a resource already registered in the process with its original device_id, instead of changing it to the requested device. (#3510)