Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 31 May 2001 19:32:51 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Addressing Layout in 1.3.x
Message-ID: <20010531193251.J26180@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010531132733 DOT 03877550 AT ks DOT teknowledge DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010531090143 DOT 0263bf78 AT ks DOT teknowledge DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010531090143 DOT 0263bf78 AT ks DOT teknowledge DOT com> <20010531150106 DOT O23914 AT redhat DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010531132733 DOT 03877550 AT ks DOT teknowledge DOT com> <20010531175843 DOT B26180 AT redhat DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010531155342 DOT 03889f98 AT ks DOT teknowledge DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <5.1.0.14.2.20010531155342.03889f98@ks.teknowledge.com>; from rrschulz@cris.com on Thu, May 31, 2001 at 04:01:21PM -0700

On Thu, May 31, 2001 at 04:01:21PM -0700, Randall R Schulz wrote:
>OK. That is pretty much what I expected, but an XSB emulator hacker out 
>there was having problems that seemed like the could possibly have been 
>related to addressing issues of this sort, so I said I'd investigate. I 
>guess that the only reason I had any suspicion was some vague hunch based 
>on the existence of the "heap_chunk_in_mb" registry entry--perhaps just 
>it's granularity.

That is just a setting which controls how much memory to allocate via
VirtualAlloc.

It's certainly possible that Cygwin is using new regions of memory in
newer versions but nothing in the use falls outside of the standard
Win32 API methods for doing this.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple