René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`StridedMemoryView` should expose access to the producer stream if possible","articleBody":"In an offline discussion it was brought to my attention that some use cases need a way to order the producer stream *after* the consumer one, when the work is done. (Ex: a ping pong exchange between producer/consumer in a tight loop.) \n\nRight now, `StridedMemoryView` follows both DLPack and CAI and does the hand-shake (stream ordering) only once. But a second ordering can be done if the producer stream is exposed. In general, this is not considered safe (because the producer may not guarantee the stream pointer is always valid during the lifetime of a `StridedMemoryView` instance). However, we do have one situation that guarantees the pointer lifetime, which is when `StridedMemoryView` instances are created inside a `@args_viewable_as_strided_memory` context (WIP in #247). In this case, before the decorated function returns the producer stream is considered always valid, and by exposing it we allow users to perform such ordering before this function returns, e.g.\n```python\n@args_viewable_as_strided_memory((0,))\ndef my_func(arr, work_stream):\n    # work_stream is a \"consumer\" stream\n    view = arr.view(work_stream.handle)\n    assert isinstance(view.producer_stream, Stream)\n    # ... do work on work_stream ...\n    view.producer_stream.wait(work_stream)\n    return\n```","author":{"url":"https://github.com/leofang","@type":"Person","name":"leofang"},"datePublished":"2024-12-02T04:00:40Z","url":"https://github.com/NVIDIA/cuda-python/issues/259"}