> but most people can live with the overcommit, as witness the fact that > most of us do and never know it. > > If you can't live with overcommit, maybe you need a wrapper that: > sets up to catch the note (I am assuming here that you get one; do you?) > malloc > zero memory you malloc'ed (which will get the pages in) > die reasonably if you get the note
but why introduce unpredictability? who really programs as if memory is not overcommited? i would bet that acme and most residents of /sys/src/cmd could do quite bad things to you in these cases. there's no waserror() in userland to wrap around memset. how much memory can be wasted by assuming that all brk'ed memory can be used? - erik
