Linux 2.4.23-rc5
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
On Tue, 25 Nov 2003 17:50:20 +0100, you wrote in linux.kernel:
Quoted 3 lines
"
overcommit_memory< 0" supposed to not allow apps to overallocate
memory - but still it works not like it is said inDocumentation/filesystems/proc.txt.
That file mentiones setting overcommit_memory to 0 to disable overcommit. Have you tried that?
Signature · 2 lines
Ciao, Pascal
Quoted 9 lines · Pascal Schmidt
On Tue, 25 Nov 2003 17:50:20 +0100, you wrote in linux.kernel:
Quoted 2 lines
"
overcommit_memory< 0" supposed to not allow apps to overallocate
memory - but still it works not like it is said inDocumentation/filesystems/proc.txt.That file mentiones setting
overcommit_memoryto 0 to disable overcommit. Have you tried that?
Yes. This is kernel default on all my systems.
Signature · 7 lines
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
Because the kernel depends on it existing. "init" |_|*|_|
literally _is_ special from a kernel standpoint, |_|_|*|
because its' the "reaper of zombies" (and, may I add, |*|*|*|
that would be a great name for a rock band).
-- Linus TorvaldsOn Tue, 25 Nov 2003 17:50:20 +0100, you wrote in linux.kernel:
Quoted 3 lines
"
overcommit_memory< 0" supposed to not allow apps to overallocate
memory - but still it works not like it is said inDocumentation/filesystems/proc.txt.
Actually, looking at vm_enough_memory in mm/mmap.c in 2.4, which seems to be the only user of sysctl_overcommit_memory, it is just used directly in an if clause:
if (sysctl_overcommit_memory) return 1;
This means any value different from 0 will turn overcommit on, no matter whether positive or negative value.
Documentation bug, I would say.
Signature · 2 lines
Ciao, Pascal