Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Mon, 3 Jul 2000 22:53:57 -0400
To:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	copy-on-write
Message-ID:	<20000703225357.A25565@cygnus.com>
Reply-To:	cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To:	cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.2i

I spent part of my "day off" today hacking together a "copy-on-write"
implementation for copying the heap after a fork.  I've long wanted to
try to do something like this.  It seems to work pretty well as long as
I don't fork something that forks something else.

I can't tell if there is a performance improvement or degradation or not
yet.

I hope that nobody is standing while reading this because I have some
shocking news.

The copy-on-write functionality is badly broken on Windows 95, so I
can't use it there.  This only works on NT.

cgf

- Raw text -