Skip to content

GH-133136: Revise QSBR to reduce excess memory held #135473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nascheme merged 10 commits into from
Jun 25, 2025
Merged

GH-133136: Revise QSBR to reduce excess memory held #135473

Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
7ef2e30
gh-133136: Limit excess memory held by QSBR
colesbury Jun 3, 2025
ce9232b
Fix unused function warning
colesbury Jun 3, 2025
3978e35
Re-work QSBR deferred advance and processing.
nascheme Jun 11, 2025
0b276ab
Update comments.
nascheme Jun 13, 2025
7ea28ff
Revise based on review feedback.
nascheme Jun 16, 2025
d2f5acc
Revert change to _Py_qsbr_advance().
nascheme Jun 17, 2025
ee13392
Call _PyMem_FreeDelayed() from eval breaker.
nascheme Jun 17, 2025
b568dbb
Merge branch 'origin/main' into gh-133136-qsbr-defer-process
nascheme Jun 17, 2025
f5f7a3f
Merge 'origin/main' into gh-133136-qsbr-defer-process
nascheme Jun 25, 2025
03f01b0
Avoid overflow in deferred memory accumulators.
nascheme Jun 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Revert change to _Py_qsbr_advance(). 
Since _Py_atomic_add_uint64() returns the old value, we need to add
QSBR_INCR.
  • Loading branch information
@nascheme
nascheme committed Jun 17, 2025
commit d2f5acc113599265ff3f89a2d88653119a6ae002
2 changes: 1 addition & 1 deletion Python/qsbr.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ _Py_qsbr_advance(struct _qsbr_shared *shared)
// NOTE: with 64-bit sequence numbers, we don't have to worry too much
// about the wr_seq getting too far ahead of rd_seq, but if we ever use
// 32-bit sequence numbers, we'll need to be more careful.
return _Py_atomic_add_uint64(&shared->wr_seq, QSBR_INCR);
return _Py_atomic_add_uint64(&shared->wr_seq, QSBR_INCR) + QSBR_INCR;
}

uint64_t
Expand Down