kkraus14 commented on PR #34972: URL: https://github.com/apache/arrow/pull/34972#issuecomment-1505405339
> Ok, who is supposed to be the consumer of the C Device Data Interface? I would expect it to be an Arrow implementation, or an Arrow-compatible library. I agree it would be primarily other libraries who want to exchange Arrow data. Users would likely initiate the exchange between the two libraries and the C Device Data Interface would be an implementation detail of how that exchange would work. I do think there would be some users who want to directly interact with the C Device Data Interface structs though as well, as I had seen similar with `__cuda_array_interface__` and dlpack. > Realistically they probably already deal with CUDA streams if they support CUDA? Not necessarily. There's a bunch of CUDA code out in the wild that just uses the default stream implicitly. For example, most numba and cupy cuda code I've seen doesn't use streams. Numba and CuPy internally both support using CUDA Streams but I don't think it would make sense for either of them to directly support the Arrow C Device Data Interface since it doesn't match their memory layout. So that would become a library author or user's responsibility to handle it and CUDA Streams / Events may be a new concept to them. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
