oneapi-src / oneapi-src/unified-runtime
Investigate how to meld USM and Virtual Memory
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
In https://github.com/oneapi-src/unified-runtime/pull/525 a number of virtual memory interfaces are added as part of supporting the sycl_ext_oneapi_virtual_mem extension. Discussion on the PR starting here points out concearns that USM and these new virtual memory interfaces are not currently well integrated.
This issue exists to track the discussion about how to meld the USM and Virtual Memory interfaces to interoperate nicely, likley in the adapter implementations, to retain memory tracking capabilities currently available in USM across all memory interfaces.
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 reading PR 525 and the discussion linked from its comments to understand the virtual memory interfaces and the USM concerns. Investigate the adapter implementations mentioned in the issue, and define completion as USM and virtual memory interoperating while retaining USM memory-tracking capabilities across the interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100