From: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject: RE: DLL Data and Copy-on-write (was RE: Why is cygwin.dll?)
20 Jan 1997 21:24:24 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <009AEAA9.0882BF40.7687.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To: colin AT bird DOT fu DOT is DOT saga-u DOT ac DOT jp
Original-CC: gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hi, you wrote:

: NT does copy on write. When calling VirtualAlloc:
[...]

I'd also like to see COW used by fork().
[Reminds me about system() and [v]fork(), you'll read that soon!]

After all, modern unixes don't have it just for fun,
it results in better performance and response time and lower resource
usage, as only a small portion might be actually modified.
But I can understand if implementing it has lower priority...


Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".