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)

  • Importing the same memory pool more than once in one process, for example by passing a raw file descriptor to PinnedMemoryResource.from_allocation_handle() twice, no longer breaks the other imports when one of them is closed. The driver returns the same pool for every import, and closing one import used to revoke device access to the pool for all of them, so device access to a pinned pool failed with CUDA_ERROR_INVALID_VALUE. All imports of a pool now share one owner, which revokes access and destroys the pool when the last of them is released. Concurrent imports of the same allocation handle from several threads now return the same memory resource instead of raising an internal error. (#3510)