cuda.core: a second grow of a grown VMM buffer fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- backend
Research direction
Start with the cuda.core VMM buffer grow slow path described in the issue, focusing on buf.handle, aligned_prev_size, and the cuMemMap call. Review ownership redesign epic #2906 and the behavior in #2880; done means a second grow no longer fails from the handle-size mismatch and a failed grow leaves the old buffer intact.
Written by the indexing model from the issue text.
Description
After one grow a buffer is backed by two physical chunks. The slow path retains only the handle of the mapping at buf.handle and maps aligned_prev_size bytes from it, but cuMemMap requires the size to equal the handle's full size, so the second grow fails. On main the attempt also unmaps the old range first and cannot restore it; with #2880 the old buffer stays intact and the grow raises cleanly. Fix belongs to the ownership redesign (epic #2906).
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 113
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.
More from NVIDIA/cuda-python
-
bug cuda.core
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NVIDIA/cuda-python#2886 · 1 comment ·
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NVIDIA/cuda-python#2717 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
NVIDIA/cuda-python#2712 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NVIDIA/cuda-python#2646 · 1 reaction ·
-
cuda.core triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NVIDIA/cuda-python#2435 · 1 comment ·
All issues in NVIDIA/cuda-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·