Repository navigation
fix(cuda): retain pinned sources across transfer failures - #10712
Conversation
Merging this PR will degrade performance by 14.95%2 warnings, 1 note
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes
|
1f87c45 to
40f13e2
Compare
Validate the transfer context and wait for the previous source fence before replacing it. On submission or fence failure, synchronize the stream before recycling the source, retaining the allocation if completion cannot be established. Include ownership regression tests and bind the context explicitly before pinned allocation. Original-commit: 94897853df Original-commit: a2f6ce3b37 Signed-off-by: Alexander Droste <alexander.droste@protonmail.com>
40f13e2 to
cd9ea47
Compare
Problem
A failed or resubmitted transfer can recycle pinned source memory before its previous DMA completes.
Solution
Check contexts, wait on the previous source fence, and establish completion before recycling buffers.
Assessment
If completion cannot be established, retain the allocation rather than risk freeing active DMA memory. Based on #10726; prerequisite for #10713.