X-Spam-Check-By: sourceware.org
Date: Tue, 10 Jan 2006 10:48:18 -0600
From: Brian Ford <Brian DOT Ford AT flightsafety DOT com>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: vfork alternatives?
Message-ID: <Pine.CYG.4.58.0601101036490.1280@PC1163-8460-XP.flightsafety.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

We have an application that mmaps a *huge* MAP_PRIVATE|MAP_ANON virtual
address scratch space.  It also needs to occasionally fork/exec a sub
process.  Unfortunately, the time and virtual memory required for Cygwin
to copy this region to the forked child just so it can throw it away and
do an exec is prohibitive if it's even possible.

I know that a real vfork has been tried without success so far, but I was
wondering if anyone had any suggestions to work around this specific type
of issue?  Maybe some no copy flag to mmap?

As an aside, one of our developers made a simple system() replacement via
CreateProcess that was working in 1.5.18.  In 1.5.19, Cygwin environment
variables are no longer passed along via his mechanism.  I know that
subverting Cygwin in this way is not supported, and I'd like a more
general solution, so I haven't yet tried to figure out what broke or if
there is still a way around it.

Any rough suggestions for a way for us to help Cygwin cope with this kind
of scenario would be greatly appreciated.  Thanks.

-- 
Brian Ford
Lead Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...


--
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/