Den 16-Mar-00 13:15:39 skrev James Sutherland f�lgende om "Re: Some questions about linux kernel.":
> No - quite the opposite. I had 0 in /proc/sys/vm/overcommit_memory. All
> that happened was the compiler processes grabbed all the VM I had,
> malloc() started returning zero, things started dying when they couldn't
> get the memory they needed.
Gcc checks its memory allocations and exits if they fail. That clearly
didn't happen. The reason of course is that putting 0 into
/proc/sys/vm/overcommit_memory is darn close to a no-op. What you saw was
the effect of overcommitting memory. The "No memory for process xxx"
messages on the console could have told you that.
Regards,
/��������������������������������T���������������������������������������\
| Rask Ingemann Lambertsen | E-mail: mailto:rask@kampsax.dtu.dk |
| Please do NOT Cc: to me or the | WWW: http://www.gbar.dtu.dk/~c948374/ |
| mailing list. I am on the list.| "ThrustMe" on XPilot, ARCnet and IRC |
| Machine-independent: Does not run on any existing machine. |
-
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 : Thu Mar 23 2000 - 21:00:28 EST