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
X-Apparently-From:	<earnie?boyd AT yahoo DOT com>
Message-ID:	<3A549C9C.F93B5160@yahoo.com>
Date:	Thu, 04 Jan 2001 10:54:04 -0500
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To:	cygwin AT cygwin DOT com
X-Mailer:	Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	"Rist, Mark J." <mark_j_rist AT md DOT northgrum DOT com>
CC:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	Re: Using large memory segments with a telnet session
References:	<C12E8508FB1BD211BDFD00A0C9C75B6102296C61 AT xcgal005 DOT al DOT essd DOT northgrum DOT com>

"Rist, Mark J." wrote:
> 
> Thanks to the archive of this mailing list, I have discovered that you can
> use large memory segments with cygwin by modifying the registry key:
> 
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
> 
> and adding the value heap_chunk_in_mb (DWORD set to max memory amount).
> 
> The problem that I am having is that I am logged into a machine via telnet
> using
> the inetutils. It appears that the registry setting is ignored for telnet
> sessions. So
> I can't run large memory programs when logged in remotely.
> 
> The problem may be exaggerated by the fact that I am using roaming profiles
> and the registry for the user I am logging in as is stored remotely.
> 
> I have tried several things to no avail:
> 1. Setting HKLM\Software\Cygnus Solutions\Cygwin\heap_chunk_in_mb
> I thought this might work since system wide mount points seem to be working
> and these are set under HKLM. Didn't work.
> 2. Setting HKCU\Software\Cygnus Solutions\Cygwin\heap_chunk_in_mb for the
> user running the inetd service. Nope.
> 
> I am running out of ideas. I am fairly sure that I can recompile the
> cygwin1.dll and
> change the default heap size to get around this problem, but I would prefer
> to
> handle this as a configuration so that I don't have to recompile for every
> release.
> 
> Any ideas?
> 

Using the source I find:

 /* Note that reserving a huge amount of heap space does not result in
 swapping since we are not committing it. */
 /* FIXME: We should not be restricted to a fixed size heap no matter
 what the fixed size is. */

 heap_chunk_in_mb = reg.get_int ("heap_chunk_in_mb", 128);
 if (heap_chunk_in_mb < 4)
   {
     heap_chunk_in_mb = 4;
     reg.set_int ("heap_chunk_in_mb", heap_chunk_in_mb);
   }

So if your program isn't finding the registry key then the heap_chunk is
4mb not 128mb.  Also, you can see in the comments that there is no
reason for a fixed limit other than no one has patched the source yet. 
So, please, fix it and submit the patch to cygwin-patches AT cygwin DOT com for
consideration.  You'll need to do the legal paper work with the release
forms at http://cygwin.com.

Cheers,
Earnie.

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

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

- Raw text -