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
I'm trying to convert my owlDeviceBuffers into owlManagedMemoryBuffers, to enable device-side memory oversubscription. However, since owlBufferUpload isn't implemented for owlManagedMemoryBuffers, I need to refactor my code to instead memcpy into a pointer through owlBufferGetPointer(). owlBufferGetPointer then wants me to specify which device the buffer belongs to, but managed memory and host memory don't belong to a particular device, so this is somewhat confusing.
If owl were to implement the same owlBufferUpload API for both managed memory buffers and host mapped buffers, it would be easier to refactor code to make the switch back and forth.
The text was updated successfully, but these errors were encountered:
natevm
changed the title
owlBufferUpload not implemented for managed memory buffers, host mapped buffers
Feature request: owlBufferUpload not implemented for managed memory buffers, host mapped buffers
Apr 3, 2020
Is this issue still active? According to the code I just looked at upload is implemented for both host-pinned an managed mem buffers; the only functionality that's not "trivially" implemented is buffer upload to a specific device ID, because for host-pinned and managed memory buffers this doesn't really make sense. (though even for those there are proper and error messages in that case
)
More of a feature request than an issue.
I'm trying to convert my owlDeviceBuffers into owlManagedMemoryBuffers, to enable device-side memory oversubscription. However, since owlBufferUpload isn't implemented for owlManagedMemoryBuffers, I need to refactor my code to instead memcpy into a pointer through owlBufferGetPointer(). owlBufferGetPointer then wants me to specify which device the buffer belongs to, but managed memory and host memory don't belong to a particular device, so this is somewhat confusing.
If owl were to implement the same owlBufferUpload API for both managed memory buffers and host mapped buffers, it would be easier to refactor code to make the switch back and forth.
The text was updated successfully, but these errors were encountered: