Xref: utzoo comp.unix.questions:31858 comp.lang.c:39760
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!tdatirv!sarima
From: sarima@tdatirv.UUCP (Stanley Friesen)
Newsgroups: comp.unix.questions,comp.lang.c
Subject: Re: Finding/changing max memory size available
Message-ID: <13@tdatirv.UUCP>
Date: 31 May 91 19:19:44 GMT
References: <24817@unix.SRI.COM> <1991May30.103731.28593@thunder.mcrcim.mcgill.edu>
Reply-To: sarima@tdatirv.UUCP (Stanley Friesen)
Followup-To: comp.unix.questions
Organization: Teradata Corp., Irvine
Lines: 18

In article <1991May30.103731.28593@thunder.mcrcim.mcgill.edu> mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes:
>In article <24817@unix.SRI.COM>, ric@ace.sri.com (Richard Steinberger) writes:
>> What I'd like to know is, "Where/How is this limit set?

>This limit is a complex interaction of several things.
<<excellent list deleted>>
>
>- Probably something else I've forgotten.

mmap() (or shmat()) may map a file or shared memory segment only a few K
above the top user address, efectively placing a roadblock in the way
of sbrk(), and thus limiting malloc().

I have seen this happen - malloc() returning NULL in a large virtual
address space because the next block of addresses was used.
-- 
---------------
uunet!tdatirv!sarima				(Stanley Friesen)