This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: vfork implementation
On Tue, Jul 27, 1999 at 06:31:58PM -0700, Earnie Boyd wrote:
>--- Chris Faylor <cgf@cygnus.com> wrote:
>> In benchmarks, this vfork is *at least* twice as fast as a normal fork.
>
>This is worth including it in the next release.
>
>> So what do you think? Is this good enough to go into the mythical next
>> net release (B21)? Should I make it a cygwin option, i.e.
>> CYGWIN=fastvfork?
>
>Not worth doing, the code I've seen that contains vfork always checks to see if
>it's available. If you don't want it just undefine the HAVE_VFORK or what ever
>macro.
The problem is that cygwin has always implemented vfork but it has always just
been implemented as a call to fork. I can't just not implement it and, on
reflection, I don't think that the current implementation is quite right.
I'll probably implement Sergey's suggestion and then it should be 100% like
BSD vfork.
cgf