oneapi-src / oneapi-src/unified-memory-framework
Does provider_tracking support split/merge ops if IPC handle is created and cached before?
Open
Nobody has claimed this yet.
question
- Dominant language
- C
- Stars
- 98
- Forks
- 48
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 6
Description
Not sure if provider_tracking supports split/merge operations correctly when the IPC handle is created and cached before we split/merge the memory region?
Ref: #429
Contributor guide
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 reviewing issue #429 and the provider_tracking handling of IPC handles, then trace what happens when a handle is cached before a memory-region split or merge. Done means establishing whether both operations are supported correctly and documenting or reproducing any failure found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100