X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=OLkW3ZPx7BOQlCgyIQMwhLkoA1qyT/M57iCSRGP3NYyfgIrgimYQ3
	rIpm4vK+wHWGYYlhElSrCWjerDp5Tgcc/iqn02fNHLUqqxFk/7EKQo118r5YoWP5
	8tvth81s1Ij5D9KjVYcr5MUQYKphin0ZBd5GfSp2zXBy7jD5ZHAp+s=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=2rj9tvW9W54O2xtoL2dXuug8/mY=; b=UhmIJnYrUXZsnARNqrt6mN2OIR2w
	zvewTIan/6VYt4psQUz9opXASq2ElMiHF8R+qNjwiXurgWqsWtTuEMSDs7xDikEI
	x3v6UYNeqrt0xYltR3pALtRmTIExGSCwbDTj6DtYk46jeIt5WQsMPWUeui8GUm78
	VNio39e5lNFX31Y=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.8 required=5.0 tests=AWL,BASE64_LENGTH_79_INF,BAYES_00,FSL_HELO_BARE_IP_2,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:1401, H*MI:sk:2016042, corporate
X-HELO:	plane.gmane.org
To:	cygwin AT cygwin DOT com
From:	Achim Gratz <Stromeko AT NexGo DOT DE>
Subject:	Re: Process map and fork problems
Date:	Wed, 20 Apr 2016 11:24:32 +0000 (UTC)
Lines:	1
Message-ID:	<loom.20160420T131743-463@post.gmane.org>
References:	<loom DOT 20160420T121651-786 AT post DOT gmane DOT org> <20160420104633 DOT GA26118 AT calimero DOT vinschen DOT de> <loom DOT 20160420T124825-644 AT post DOT gmane DOT org> <20160420111431 DOT GB13570 AT calimero DOT vinschen DOT de>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id u3KBPJTU028298

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > I think all the affected machines have 4GB memory installed, but the
> > option may not have been default when they were installed.
> 
> They never are default.  Default is 2 Gigs application VM, 2 Gigs
> kernel̇ memory space.  Specifying /3Gb means 3 Gigs application VM
> vs. 1 Gig kernel̇ memory space.  That's not always a good thing
> since it could lead to kernel memory pool exhaustion.

I meant "not default in the base install image provided by corporate IT". 
I'll have to ask if they have some special procedure to switch it on.

> > With /3GB you mean 4GT (aka PAE), right?  And 32bit is without PAE?
> 
> No, PAE works differently, using different calls.  I'm talking abut
> the normal 32 bit address space of a 32 bit CPU.

Hmm.  Microsoft's 4GT documentation makes you believe that /3GB and PAE is
always coupled, though.  But then even non-/3GB might laready use some PAE
facilities anyway.  But I guess it's not important.

> It can only know its own heap.  But keep in mind that the heap can
> be differently sized in different applications.  The heap only *starts*
> as a 384Meg heap, it could easly grow in big apps (gcc, emacs, ...)
> when calling sbrk.

So it can grow only so much until it runs into the first loaded DLL above? 
Or does it fragment into yet unused areas then?


Regards,
Achim.

- Raw text -