Skip to content

Add memory policy support #4726

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

askervin
Copy link
Contributor

Implement support for Linux memory policy in OCI spec PR: opencontainers/runtime-spec#1282

TODO:

  • remove the replace from go.mod when OCI spec is merged

@askervin askervin force-pushed the 5aD-oci-mempolicy branch 10 times, most recently from 66df434 to cde25df Compare April 22, 2025 06:48
@askervin askervin changed the title [DO NOT MERGE] Add memory policy support Add memory policy support Apr 22, 2025
@askervin
Copy link
Contributor Author

@AkihiroSuda, @giuseppe, do you think it would be good to keep this PR as Draft until opencontainers/runtime-spec#1282 is merged? Or should I make it Ready for review (despite the "replace" in go.mod) in order to get reviews and possibly get this tagged into v1.3?

@AkihiroSuda
Copy link
Member

Please keep this draft until the runtime spec PR gets merged

@askervin askervin force-pushed the 5aD-oci-mempolicy branch 2 times, most recently from b41c933 to c6a240b Compare April 23, 2025 07:30
Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
@askervin askervin force-pushed the 5aD-oci-mempolicy branch from c6a240b to 26ab8a1 Compare April 23, 2025 07:30
Implement support for Linux memory policy in OCI spec PR:
opencontainers/runtime-spec#1282

TODO:
- remove the replace from go.mod

Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
@askervin askervin force-pushed the 5aD-oci-mempolicy branch from 26ab8a1 to 3bb9611 Compare April 23, 2025 07:36
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.

2 participants