X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 25 Sep 2008 10:23:44 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem to open big selfextracting Zip files from bash - starting from scratch :-)
Message-ID:	<20080925142344.GB21100@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<48DA7010 DOT 8000003 AT oracle DOT com> <20080924170655 DOT GB24085 AT ednor DOT casa DOT cgf DOT cx> <48DB51D2 DOT 1040909 AT oracle DOT com> <01fa01c91ef1$4875a170$9601a8c0 AT CAM DOT ARTIMI DOT COM>
MIME-Version:	1.0
In-Reply-To:	<01fa01c91ef1$4875a170$9601a8c0@CAM.ARTIMI.COM>
User-Agent:	Mutt/1.5.16 (2007-06-09)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Thu, Sep 25, 2008 at 10:29:56AM +0100, Dave Korn wrote:
>Dirk Napierala wrote on 25 September 2008 09:55:
>
>>  From what we understand by reading the guideline "Changing Cygwin's
>> Maximum Memory" the result
>> of the small program written by DJ Delorie  tests the memory allocation
>> limit on your system.
>> Running the program will output the maximum amount of allocatable memory
>> of your system.
>> Doing so on several test systems and the different cygwin versions the
>> result is _always _1536.
>> Trying it for example with 2500MB setting on a 4GB system also failed
>> with "Cannot allocate memory".
>
>  There is an upper limit imposed by the dividing point between kernel and
>user space at the 2GB mark.  You can try adding the /3GB flag in boot.ini to
>raise this by a further gig.  You might need also to make extensive use of
>rebaseall to ensure your DLLs end up at the upper end of that range and don't
>fragment the space, or it might not matter, depending on the patterns of
>memory usage of the unpacker.

Right.  Also, the User's Guide entry is out of date.  The example maxmem
allocator won't tell you what the maximum contiguous amount of memory
possible could be.  That's what the heap_chunk_in_mb sets.  The new
malloc allows discontiguous allocation but is still limited to available
memory holes.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -