Tianqi Chen
Tianqi Chen
On event, you are right one issue is the implementation complexity, indeed deleter lifecycle would be one issue (where-as in case of torch it can be added complexity). From the...
Thanks @kkraus14 , I think the main spirit is that Option C is kinda of the common usecase that we would like to support. In the above example, we kinda...
Thanks @kkraus14 , I agree A1 would be the more preferred ideal flow. `__env_stream__ ` is something that is already resembled in the `DLPackManagedTensorFromPyObject` proposal, it is effectively `optional_out_env_stream`. I...
Updated after some discussions, I think it is clear there are generally two kinds of consumer needs for DLPack exchange: - N0: library support, where consumer.kernel(x, y, z) would like...
I think it is harder to guarantee "long term" safety on stream in general, so for the case of N0, very likely we only launch on the `DLPackCurrentWorkStream ` and...
Send a followup note, we have updated the proposal to focus on usecases of N0, please see latest updates here https://github.com/dmlc/dlpack/issues/175
cc @mshr-h can you help to take a look
Thanks a lot for the note, we have a fix for this and will work to ship in upcoming patch release
As of now it was still internal NV, but hopefully it should come out around 4.3.1
that is right, fix is to update to restore device