Re: [debian-knoppix] Undefined behaviour after some uptime
Am Samstag, 4. Januar 2003 00:31 schrieb Nils Magnus:
> Thanks Valentijn, that info was most helpful, I was not aware of this
> implementation and was most probably influenced by the romantic but yet
> naive ideas my professor told me a couple of years ago (in turn
> influenced by Tannenbaum and other "dreamers" ;), that there should
> never be more (possibly dirty) entires in the page tables than there is
> physical memory plus swapspace.
>
> Did I understand it right, that "opportunistic memory allocation" and
Well, I'd call overcommitment, but opportunistic is probably also a correct
description. Compare also to opportunistic lock management in Databases and
Version management systems.
> /proc/sys/vm/overcommit_memory are more or less the same?
>
> The short description from Rik was quite helpful:
>
> http://linux-mm.org/docs/oom-killer.shtml
>
> However, the unresolved question remains then, why I encounter these
> situations still with a 2.4.20?
Well, probably not from overcommitment. You can still get out of memory
conditions without overcommitment. It's just more difficult :)
root@andi-lap:/home/andreas# echo 1 >/proc/sys/vm/overcommit_memory
root@andi-lap:/home/andreas# ./testmem
/proc/meminfo makes me to malloc 644468 KB RAM
res=0x40130008
root@andi-lap:/home/andreas# echo 0 >/proc/sys/vm/overcommit_memory
root@andi-lap:/home/andreas# ./testmem
/proc/meminfo makes me to malloc 644468 KB RAM
res=(nil)
Andreas
_______________________________________________
debian-knoppix mailing list
debian-knoppix@linuxtag.org
http://mailman.linuxtag.org/mailman/listinfo/debian-knoppix
Reply to: