oneapi-src / oneapi-src/unified-memory-framework
Handle case where trackingAlloc() got OOM on umfMemoryTrackerAdd()
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 98
- Forks
- 48
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 6
Description
Currently, we first call umfMemoryProviderAlloc() and then the umfMemoryTrackerAdd(). Ideally, we shouldn't call the provider if we run out of memory during umfMemoryTrackerAdd() so we have to reserve memory for the tracker entry at a first step.
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 tracing trackingAlloc(), umfMemoryProviderAlloc(), and umfMemoryTrackerAdd() to understand their current error paths. Verify how tracker-entry reservation and provider allocation interact under OOM, with completion defined as avoiding provider allocation when tracker insertion cannot succeed and preserving correct failure handling.
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
- Mostly clear
- Newbie friendliness
- 35/100