Skip to content
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.

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

No scanning an object twice in each GC. #120

Merged
merged 1 commit into from
Jan 10, 2025
Merged

Conversation

wks
Copy link
Collaborator

@wks wks commented Jan 10, 2025

This PR forces each object to be scanned at most once in each GC. In this way, no two GC workers will scan the same object at the same time. This can solve some potential problems such as data races in cleaning the code cache. Currently this only affects the MarkSweep plan.

This PR forces each object to be scanned at most once in each GC.  In
this way, no two GC workers will scan the same object at the same time.
This can solve some potential problems such as data races in cleaning
the code cache.  Currently this only affects the MarkSweep plan.
@wks wks merged commit 1776af2 into mmtk:master Jan 10, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant