-
Notifications
You must be signed in to change notification settings - Fork 137
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
low memory handling #1130
Labels
Comments
francescolavra
added a commit
that referenced
this issue
Jul 15, 2022
With this change, it is possible to register different "memory cleaner" closures, which will be invoked to free up memory when the system is low on available physical memory. The virtio balloon deflater and the pagecache drain function have been converted to use this interface. Partially addresses #1130.
francescolavra
added a commit
that referenced
this issue
Jul 29, 2022
With this change, it is possible to register different "memory cleaner" closures, which will be invoked to free up memory when the system is low on available physical memory. The virtio balloon deflater and the pagecache drain function have been converted to use this interface. Partially addresses #1130.
francescolavra
added a commit
that referenced
this issue
Aug 6, 2022
With this change, it is possible to register different "memory cleaner" closures, which will be invoked to free up memory when the system is low on available physical memory. The virtio balloon deflater and the pagecache drain function have been converted to use this interface. Partially addresses #1130.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need a heuristic and global facility for detecting low memory situations and triggering drain functions around the various caches and free lists that exist in the kernel (page cache, object caches, etc). This is open to interpretation / design.
Related: #1125, #1117, #1079, #660
The text was updated successfully, but these errors were encountered: