Traverse-Research / Traverse-Research/gpu-allocator
Vulkan allocator should determine limits based off what the user passes in, not what Vulkan reports
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 497
- Forks
- 82
- Avg merge
- 18d 17h
- Merged PRs (30d)
- 1
Description
The reason this may be desirable is to allow limiting how many resources the allocator may consume. This is required to safely have a vulkan renderer that also hosts a wgpu device as a guest on the same logical device (such as with #125 where the memory limits being exceeded is undefined behavior).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the allocator currently derives resource limits from Vulkan-reported values and where user-provided limits could enter. Use issue #125 as the coexistence scenario; done means caller-supplied limits constrain allocator consumption when sharing a logical device with a wgpu device, without relying solely on Vulkan's reported limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100