> 1) if a process writes to memory when the memory isn't really there,
> the process is stopped by the scheduler, and cannot run again until
> it can get its memory. Could be some security problems and/or
> deadlocks here.
This is already done. Writing to non-existant memory will cause
a page fault. If the address space isn't reserved either, it
will cause a segmentation fault too.
> 2) when reach OOM, make a new swap file. Other OS's use growable
> swap, why not linux?
What do you do when you run out of growable swap too? My
OOM patch is basically a band-aid for when that happens,
but I won't keep you from implementing growable swap for
Linux...
> 4) Maybe there is a way to more carefully arrange the swap+memory so
> that conflicts are less likely.
See Andrea's patch for something along those lines.
(but don't try it yet. Andrea is like me, you'll often have
to wait for the 2nd patch to get something actually working :)
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/