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
For other device types which do have a stream, queue or similar synchronization mechanism, the most appropriate type to use for `stream` is not yet determined. E.g., for SYCL one may want to use an object containing an in-order ``cl::sycl::queue``. This is allowed when libraries agree on such a convention, and may be standardized in a future version of this API standard.
246
247
247
-
**Note**
248
+
**Tip**
248
249
249
-
Support for a ``stream`` value other than ``None`` is optional and implementation-dependent.
250
+
It is recommended that implementers explicitly handle streams. If
251
+
they use the legacy default stream, specifying ``1`` (CUDA) or ``0``
252
+
(ROCm) is preferred. ``None`` is a safe default for developers who do
253
+
not want to think about stream handling at all, potentially at the
254
+
cost of more synchronization than necessary.
250
255
251
-
Device-specific notes:
256
+
Returns
257
+
-------
258
+
capsule: PyCapsule
259
+
a DLPack capsule for the array. See :ref:`data-interchange` for details.
260
+
261
+
Notes
262
+
-----
263
+
- Support for a ``stream`` value other than ``None`` is optional and implementation-dependent.
264
+
- Device-specific notes:
252
265
253
-
**CUDA**
266
+
**CUDA**
254
267
255
268
- ``None``: producer must assume the legacy default stream (default).
0 commit comments