From 78045cc93482b9f23335a36eb7841e4a29a8cde1 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Tue, 4 Feb 2025 21:13:31 +0100 Subject: Note about vm_page_evict probably being the one to care about swap size --- open_issues/mach-defpager_swap.mdwn | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'open_issues') diff --git a/open_issues/mach-defpager_swap.mdwn b/open_issues/mach-defpager_swap.mdwn index 2363bb9f..78290d71 100644 --- a/open_issues/mach-defpager_swap.mdwn +++ b/open_issues/mach-defpager_swap.mdwn @@ -21,11 +21,14 @@ lose it. The corresponding object will trigger SIGBUS on access to lost data (hopefully killing the corresponding process, thus releasing memory). GNU Mach should be aware of how much is left, to better manage paging out, -possibly throttling some processes. Hopefully ext2fs will be able to flush out +possibly throttling some processes. Hopefully ext2fs will be able to page out dirty data and release memory. With overcommit control we can then avoid one process filling the whole memory+swap with anonymous data. If several processes cooperate in sucking memory, we'd have to OOM some of them. +E.g. `vm_page_evict` would know not to try to evict an internal page, and just +wait for the external pages to get paged out and get released. + # IRC, OFTC, #debian-hurd, 2012-06-16 I allocated a 5GB partition as swap, but hurd only found 1GB -- cgit v1.2.3