Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin AT cygwin DOT com>
Subject: RE: OT: possible project/research project
Date: Wed, 20 Mar 2002 21:31:33 -0600
Message-ID: <NCBBIHCHBLCMLBLOBONKAEAFCMAA.g.r.vansickle@worldnet.att.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <013a01c1cff2$e515c910$0200a8c0@sknet01>
Importance: Normal

> I would certainly agree with you about that, but the fact remains, a lot
> of code, that cygwin exists to ease the porting of, uses it. If the work
> was done on fork itself, it would help speed-up a lot more that just
> configure (or similar) scripts.
>
> Stephano Mariani

The thing is, a lot of work *has* been done to make fork as efficient as
possible.  But there's a limit on how fast you can create a new process and
duplicate the current one into it.  And Windows doesn't go out of its way to
help.

--
Gary R. Van Sickle
Brewer.  Patriot.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/