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
A long-standing missing feature. Some of the basic logic is currently there, but a lot more is needed. In particular:
Buffer and image state tracking needs to track what memory is bound where at any given time. Not just for validation purposes, but also to keep the memory allocations alive.
When submitting a command buffer, checks should be performed to ensure that all the accessed regions of buffers and images in that command buffer have memory bound to them. This needs to take into account sync ordering (sparse binds are not ordered unless synced with semaphores).
How should sparse binding interact with subbuffers?
How to deal with host access? Sparse memory is not contiguous, so the current read and write methods, which return a slice, don't work.
The text was updated successfully, but these errors were encountered:
I have been using sparse images with vulkano where I manually manage allocations and binding. I had to make a few small changes to vulkano though:
Uncomment ImageCreateFlags::SPARSE_BINDING etc
Make Image::from_raw() public
Make RawImage::get_sparse_memory_requirements() public
Would you accept a PR with such changes? I recognise that this does not actually help with adding safe sparse image support to vulkano, but it is enough for my use case.
A long-standing missing feature. Some of the basic logic is currently there, but a lot more is needed. In particular:
read
andwrite
methods, which return a slice, don't work.The text was updated successfully, but these errors were encountered: