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 the C-Data API assumes that all the buffers are CPU buffers and there is no way to pass device information through the ABI to allow using it for non-cpu memory allocations. We need to enhance the API to allow passing device and memory information without breaking the C-Data ABI, while also ensuring it is future-proofed for future developments with non-cpu devices.
Component(s)
Format
The text was updated successfully, but these errors were encountered:
### Rationale for this change
In order to support non-cpu devices and memory usage, we can add new `ArrowDeviceArray` and `ArrowDeviceArrayStream` structs to the C Data Interface in order to allow for handling these types of memory.
### What changes are included in this PR?
Definitions for a new `ArrowDeviceArray`, `ArrowDeviceArrayStream` and `ArrowDeviceType` enums.
* Closes: #34971
Lead-authored-by: Matt Topol <zotthewizard@gmail.com>
Co-authored-by: David Li <li.davidm96@gmail.com>
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
Co-authored-by: John Zedlewski <904524+JohnZed@users.noreply.github.com>
Co-authored-by: Gang Wu <ustcwg@gmail.com>
Signed-off-by: Matt Topol <zotthewizard@gmail.com>
Describe the enhancement requested
Currently the C-Data API assumes that all the buffers are CPU buffers and there is no way to pass device information through the ABI to allow using it for non-cpu memory allocations. We need to enhance the API to allow passing device and memory information without breaking the C-Data ABI, while also ensuring it is future-proofed for future developments with non-cpu devices.
Component(s)
Format
The text was updated successfully, but these errors were encountered: