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

[cgroups2] Add OOM listening to the MemoryControllerProcess. #578

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

DevinLeamy
Copy link
Contributor

Introduces OOM listening to the MemoryControllerProcess so that we
detect, report, and respond to OOM events.

Devin Leamy added 4 commits April 25, 2024 16:02
Introduces the `MemoryControllerProcess`, the cgroups v2 memory
isolator, which will be used by the `Cgroups2IsolatorProcess`.

Unlike the `MemorySubsystemProcess`, the cgroups v1 memory isolator, we:
- Don't allow limits on swap memory to be set.
- Don't report memory pressure levels (this facility is no longer part
  of the cgroups memory controller's API)

Future work may include:
- Adding support for swap memory, and
- Reporting the (now available) memory pressure stall information
Introduces the `MemoryControllerProcess`, the cgroups v2 memory
isolator, which will be used by the `Cgroups2IsolatorProcess`.

Unlike the `MemorySubsystemProcess`, the cgroups v1 memory isolator, we:
- Don't allow limits on swap memory to be set.
- Don't report memory pressure levels (this facility is no longer part
  of the cgroups memory controller's API)

Future work may include:
- Adding support for swap memory, and
- Reporting the (now available) memory pressure stall information
Introduces OOM listening to the MemoryControllerProcess so that we
detect, report, and respond to OOM events.
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