On Mon 1 Oct 2007 12:27, [EMAIL PROTECTED] pondered: > overcommit by default is optimistic that if the program requesting the > memory actually tries to use it there will be enough (both the fork-exec > situation and the copy-on-write memory of real forks mean that the > system ends up useing much less memory then is theoretically allocated). > > switching it to be pessimistic (overcommit 2 IIRC) means that the OOM > handler will never kick in, but it means that programs will be told that > there isn't any memory when there really is enough for the program to > work.
I have set it to 2, and still get the OOM if I malloc too much... I never get a null back from malloc, no matter what I try. -Robin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
