cuda.core: VirtualMemoryResource.modify_allocation(config=...) changes the resource's policy
Nobody has claimed this yet.
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
modify_allocation(buf, size, config=...) assigns the config to the resource before any check, so later allocate() calls and the accessibility properties use it. The docstring describes a per-call policy; test_vmm_allocator_policy_configuration asserts the persistence (see #1300). The assignment also skips the constructor's validation (RDMA support, host-location handling, dict configs). Decide per-call or persistent, then align the docstring and the test.
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 locating cuda.core's modify_allocation implementation and the resource constructor, then read test_vmm_allocator_policy_configuration and the referenced behavior from #1300. Determine whether config is per-call or persistent, including constructor validation behavior, and align the docstring and test with that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100