Messages in this thread | | | From | jmcmullan@linuxcar ... | Subject | Re: OOM in 2.2.14 | Date | 14 Jul 2000 16:34:27 GMT |
| |
Rik van Riel <riel@conectiva.com.br> wrote: > On 13 Jul 2000 jmcmullan@linuxcare.com wrote:
>> That is yet another alternative. The point is to put all >> of the process killing logic in user-land - not to quibble about >> possible implementations of such logic.
> Let me repeat myself: NO MEMORY LEFT. NADA. ZILCH. NOTHING.
So when I say that the daemon would start killing processes when it gets a message from the kernel that 90% of VM is in use, it can't run because that 10% of VM that isn't in use doesn't exist?
Color me confused. The daemon runs BEFORE an OOM, but in NEAR OOM conditions - ie. only 10% of VM left, or 5M of VM, or whatever the user set the limit to be.
The killing STARTS at 10% of VM remaining. Kind of like when filesystems reach the root-only reserve point (an old BSDism, I know...) and only root can create new files...
-- Jason McMullan, Senior Linux Consultant, Linuxcare, Inc. 412.422.8077 tel, 412.656.3519 cell, 415.701.0792 fax jmcmullan@linuxcare.com, http://www.linuxcare.com/ Linuxcare. Support for the revolution.
- 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/
| |