From: Ben Pfaff Date: Thu, 5 Oct 2006 01:25:38 +0000 (+0000) Subject: When out of memory+swap, just panic the kernel. X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?p=pintos-anon;a=commitdiff_plain;h=f40f5e8a6f70b12b8e0848f1d1484725c142f840 When out of memory+swap, just panic the kernel. --- diff --git a/doc/vm.texi b/doc/vm.texi index 2376aa1..cf4f764 100644 --- a/doc/vm.texi +++ b/doc/vm.texi @@ -313,10 +313,12 @@ implementation, be sure to retain the distinction between the two pools. The most important operation on the frame table is obtaining an unused frame. This is easy when a frame is free. When none is free, a frame -must be made free by evicting some page from its frame. If no frame can -be evicted without allocating a swap slot, but swap is full, some -process must be killed to free memory (the choice of process to kill is -up to you). +must be made free by evicting some page from its frame. + +If no frame can be evicted without allocating a swap slot, but swap is +full, panic the kernel. Real OSes apply a wide range of policies to +recover from or prevent such situations, but these policies are beyond +the scope of this project. The process of eviction comprises roughly the following steps: