Add API to allocate read-only (texture) memory
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 344
- Forks
- 79
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 27
Description
Read-only memory can be allocated via the HSA runtime, and can be potentially much faster for reads than regular global memory. We should support working with this memory via the Mem API.
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 locating the Mem API and its HSA runtime allocation path. Determine how read-only texture memory should be represented and exposed through Mem, then identify the relevant tests or examples. Done means the API supports allocating and working with this memory type and verifies the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100