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

Expose whether _default_ space for Plan can pin objects or not #1187

Open
k-sareen opened this issue Aug 21, 2024 · 2 comments
Open

Expose whether _default_ space for Plan can pin objects or not #1187

k-sareen opened this issue Aug 21, 2024 · 2 comments

Comments

@k-sareen
Copy link
Collaborator

This is useful if you want to allocate non-moving objects into the default space and pin them instead of having a separate non-moving space.

@qinsoon
Copy link
Member

qinsoon commented Aug 21, 2024

I plan to expose some info about spaces to bindings. But those are mostly for debugging, or for bindings to do optimizations for certain plans.

if you want to allocate non-moving objects into the default space and pin them instead of having a separate non-moving space.

Why do you want to use pin instead of non moving?

@k-sareen
Copy link
Collaborator Author

k-sareen commented Aug 21, 2024

Pinning needs to be enabled for the ZygoteSpace since we compact into it. And if we already have the pin bit, then we can just use that instead of having a separate non-moving space if the selected plan is Immix-based.

EDIT: This is also useful for JNI critical sections as we can just pin the object instead of deferring or disabling GC

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

No branches or pull requests

2 participants