Re: Out Of Memory in v. 2.1
Feuer (feuer@his.com)
Sun, 04 Oct 1998 23:49:53 -0400
I had five ideas
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.
2) when reach OOM, make a new swap file. Other OS's use growable swap, why not
linux?
3) Someone mentioned the problem when A must be swapped out, and B must be
swapped in, but there is no swap around for A to be swapped to. To solve this,
I would reserve at bootup a small amount (<<1K) of memory to use as a buffer.
That way the two can be interchanged through the buffer.
4) Maybe there is a way to more carefully arrange the swap+memory so that
conflicts are less likely.
Disclaimer: I know nothing about MM.
David Feuer
feuer@his.com
-
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/