Traverse-Research / Traverse-Research/gpu-allocator
Add getters to AllocationSizes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 497
- Forks
- 82
- Avg merge
- 18d 17h
- Merged PRs (30d)
- 1
Description
AllocationSizes can adjust the parameters given, it might be usefull to read them back to put a hard limit on the memory usage https://github.com/gfx-rs/wgpu/blob/afec4b73c8d5af2cbc9581ba163d143aa031daf8/wgpu-hal/src/dx12/suballocation.rs#L94-L95
Or even better, but I don't know if it's in the scope of gpu-allocator, allowing to configure a budget (upper limit) for the allocator, or something that could allow to get the size of the underlying allocation used prior to a allocate call (that would only return a size if the allocator needs to grow a block or allocate a new one and 0 if it can reuse a block)
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 with AllocationSizes in wgpu-hal/src/dx12/suballocation.rs, especially the referenced lines, and trace how its adjusted parameters are used by gpu-allocator. Clarify whether the goal is read-only getters, an allocator budget, or a pre-allocation size query. Done requires a settled API scope and behavior for the chosen option.
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
- 30/100