AW: cygwin vfork

[Christopher Faylor]

On Tue, Nov 13, 2001 at 10:43:03AM -0500, Charles Wilson wrote:
>> The VM comment is referring to the large footprint of XEmacs which means
>> that doing a fork requires copying an awful lot of data (and hence takes a
>> long time), most OS's do copy-on-write for vfork so the overhead is never
>> incurred.
>
>And of course, cgf chimed in on this thread, but I can't find his message 
>in my mail archive, and (as mentioned elsewhere) the cygwin ml archive is 
>missing his message as well, so I can't quote it here for you.

With vfork, there is very little copying going on.  Only cygwin's heap is
copied.

Of course, if you don't use vfork then cygwin's fork implementation *is*
pretty slow.

cgf

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