Re: Avoiding OOM on overcommit...?

From: Jesse Pollard (pollard@cats-chateau.net)
Date: Thu Mar 30 2000 - 19:24:58 EST


On Thu, 30 Mar 2000, James Sutherland wrote:
>On Sun, 26 Mar 2000 15:38:16 +0200 (MET DST), you wrote:
>(snip)
>>It might actually be possible nowadays to provide backing space on disk for the
>>stacks of live processes.
>There is much more to memory usage than just stack size...
>
>>Nearly everyone will have 2GB spare for 256*8MB
>>of emergency stack space.
>"Nearly everyone"? I have seen production servers with a TOTAL of that
>amount of disk space...
>
>>That about takes care of everyones problems,
>>since not walking malloced memory when you get it to make sure its
>>there is the programmers decision.
>If you want non-overcommitted behaviour, you can just use gnumalloc
>and allocate your own stack at initialisation time (or just pre-expand
>it).

And the race condition that has been pointed out before causes both to
be unreliable.

Quotas are the best known way to handle the problem.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@cats-chateau.net

Any opinions expressed are solely my own.

-
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/



This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:28 EST