You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently RMM does not document the requirement that a prefetch_resource_adaptor must wrap a managed memory resource.
Additionally, on systems where managed memory is not supported, a cudaErrorInvalidDevice occurs.
We should make prefetching a transparent fault-tolerant API, with no hard errors. This makes it easier to use prefetching as a "hint" in an application without having to conditionally check for managed memory support from the current memory resource before calling the prefetch API. In cuDF, for instance, we would like to enable prefetching as a performance optimization in many locations -- and do nothing if the memory resource isn't compatible.
The text was updated successfully, but these errors were encountered:
Following up from rapidsai/cudf#16551 (comment)
Two problems:
prefetch_resource_adaptor
must wrap a managed memory resource.cudaErrorInvalidDevice
occurs.We should make prefetching a transparent fault-tolerant API, with no hard errors. This makes it easier to use prefetching as a "hint" in an application without having to conditionally check for managed memory support from the current memory resource before calling the prefetch API. In cuDF, for instance, we would like to enable prefetching as a performance optimization in many locations -- and do nothing if the memory resource isn't compatible.
The text was updated successfully, but these errors were encountered: