Traverse-Research / Traverse-Research/gpu-allocator
Allow importing externally allocated memory into the allocator
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 497
- Forks
- 82
- Avg merge
- 18d 17h
- Merged PRs (30d)
- 1
Description
It may be desired to import memory from an os object, such as a Win32 HANDLE, Linux Dmabuf, Fuchsia VMO, etc.
Ideally the Vulkan allocator could provide a way to unsafely create a memory block from some VkDeviceMemory and some auxiliary information (such as the size of the block, memory type, etc).
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
The issue names no files, tests, or entry points. Start by surveying the allocator's Vulkan, DirectX 12, and Metal backends alongside the relevant external-memory APIs; done means an agreed and tested way to import externally allocated memory with its required metadata.
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