Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!ut-emx!ibmchs!auschs!awdprime!doorstop.austin.ibm.com!tif
From: tif@doorstop.austin.ibm.com (Paul Chamberlain)
Newsgroups: comp.unix.aix
Subject: Re: malloc (was: making a request to IBM)
Message-ID: <6913@awdprime.UUCP>
Date: 22 Apr 91 20:49:36 GMT
References: <6644@awdprime.UUCP> <6833@awdprime.UUCP> <6849@awdprime.UUCP>
Sender: news@awdprime.UUCP
Reply-To: tif@doorstop.austin.ibm.com (Paul Chamberlain)
Organization: IBM AWD, Austin
Lines: 12

jfh@greenber.austin.ibm.com (John F Haugh II) writes:
>Better would be a way to say "over commit" or "don't over commit" via
>some configuration (like SMIT) option.

How about a flag, a compile option, a special routine, or something
that an application can do, to say "Please over-commit memory for me
and you can kill me if you run out."

Then make that nasty fortran compiler do it automatically.   :-)

Paul Chamberlain | I do NOT speak for IBM.          IBM VNET: PAULCC AT AUSTIN
512/838-9748     | ...!cs.utexas.edu!ibmchs!auschs!doorstop.austin.ibm.com!tif