Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sun, 3 Jun 2001 12:05:31 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: CreateFiber() : number of fibers limited Message-ID: <20010603120531.B29241@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3B1A0E67.1A48AD8A@unidui.uni-duisburg.de> <5.1.0.14.2.20010603085539.02534088@pop3.cris.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.20010603085539.02534088@pop3.cris.com>; from rrschulz@cris.com on Sun, Jun 03, 2001 at 08:59:48AM -0700 On Sun, Jun 03, 2001 at 08:59:48AM -0700, Randall R Schulz wrote: >Don't forget about the Cygwin-wide memory allocation limit dictated by the >DWORD registry entry "heap_chunk_in_mb" (HKEY_CURRENT_USER\Software\Cygnus >Solutions\Cygwin\heap_chunk_in_mb) which defaults to 128 (megabytes). > >Where this limit typically hit me was in compiling a C program with a large >switch statement using gcc with -O4 optimization. That controls cygwin's allocation. It should have nothing to do with allocation of memory for the Windows API functions. cgf >At 03:16 2001-06-03, Holger Vogt wrote: >>independently of the requested stack size (first parameter in >>CreateFiber()), CYGWIN will give only 53 fibers. Only when I increase >>the stack size above 9.5 MByte, I will get a further reduction in the >>number of fibers created. >> >>The error by GetLastError is always no. 8, 'Not enough storage is >>available to process this command.'. >> >>Borland C++Builder Compiler (same test application) will reduce the >>number of possible fibers according to stack size. 1000 fibers are no >>problem with a stack size of 64 k Byte. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple