lkml.org 
[lkml]   [2002]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject2.4 kernel series and the oom_killer and /proc/sys/vm/overcommit_memory
Date
Hi there,

I just have one question.

If I understand it correct, /proc/sys/vm/overcommit_memory controls if there
is "1" always enough memory and if "0" every program call checks if there is
enough memory.

I just tried to open up much Xterms until my RAM + SWAP is full. The system is
up and response is slowly for ~ 5 minutes, doing whatever, swapping or kinda
that. This was tested with overcommit_memory == 0 ... With 2.4.19, the
oom_killer comes NOT in action, after the 5 minutes the system is dead. With
2.4.18's oom_killer there are program kills at random.

My question now: Why isn't it possible, if overcommit_memory is 0, to really
check if there is enough memory or not, and if NOT just to display a message
like "Not enough memory for execution. Aborted" ?

TIA!

--
Kind regards
Marc-Christian Petersen

http://sourceforge.net/projects/wolk

PGP/GnuPG Key: 1024D/569DE2E3DB441A16
Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16
Key available at www.keyserver.net. Encrypted e-mail preferred.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.062 / U:0.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site