-
Notifications
You must be signed in to change notification settings - Fork 396
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
Add support for 32bit allocator flags #7285
Conversation
809fd3a
to
526606c
Compare
@babsingh please review these changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor nits. which new feature will be supported by these changes?
Currently, this will enable us to study the performance impacts of differing vmem modes. Longer term we would like to explore disclaiming 32bit memory at runtime and in CRIU C/R. Additionally, the ability to set 32bit allocator flags may be helpfull if we want to toggle the behaviour for special cases (eg. using vthreads or not). |
jenkins build all |
|
Introduce a mechanism to set flags for the 32bit allocator. Use the new mechanism to toggle the vmem mode to tmp file backed vmem. Signed-off-by: Tobi Ajila <atobia@ca.ibm.com>
I missed a header definition. Its fixed now. |
jenkins build all |
Only known and unrelated failures are seen: |
Introduce a mechanism to set flags for the 32bit allocator.
Use the new mechanism to toggle the vmem mode to tmp file backed vmem.