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
In #3348 (comment), it came up that we may want to consider making stream a required argument wherever a CUDA stream can be passed.
At the moment, stream is not a required parameter and defaults to None (translating to nullptr or "default stream" at the C++ layer). This aligns with underlying C++ APIs which also use stream=0 as a default (example).
However, as pointed out in the discussion above, users can forget to pass a stream in situations like the following:
withstreamass:
arr=cp.random.random(...)
reduce_into(..., d_in=arr, ...) # forgot to pass s here for whatever reason
This is seemingly a broader problem in the ecosystem (any API from any library accepting a CUDA stream has the same problem). So it would be good to hear perspectives from e.g., @vyasr as I know cuDF is also considering exposing streams in their APIs.
The text was updated successfully, but these errors were encountered:
In #3348 (comment), it came up that we may want to consider making
stream
a required argument wherever a CUDA stream can be passed.At the moment,
stream
is not a required parameter and defaults toNone
(translating to nullptr or "default stream" at the C++ layer). This aligns with underlying C++ APIs which also usestream=0
as a default (example).However, as pointed out in the discussion above, users can forget to pass a stream in situations like the following:
This is seemingly a broader problem in the ecosystem (any API from any library accepting a CUDA stream has the same problem). So it would be good to hear perspectives from e.g., @vyasr as I know cuDF is also considering exposing streams in their APIs.
The text was updated successfully, but these errors were encountered: