actually, vfork was implemted (as i understand it) due to insufficient core. fork used to swap the parent to disk and continue with the child process.
vfork was efficient if the child finished before it's scheduling quanta was used up. - erik On Sat Aug 12 12:24:41 CDT 2006, [EMAIL PROTECTED] wrote: > BUGS section of 4th BSD manual, VFORK(2V) > > ``This system call may be unnecessary if the > system sharing mechanism allow fork > to be implemented more efficiently'' > > > >> On 8/12/06, Victor Nazarov <[EMAIL PROTECTED]> wrote: > >> > POSIX-fork() copies data and bss segmets, child process doesn't share > >> > data with it's parent. > >> > >> vfork() causes both child and parent to share address space. I > >> believe this was introduced to make the fork/exec sequence faster as > >> the address space COW didn't need to be setup. > > > > I always thought vfork was introduced because > > copy-on-write hadn't been invented yet. > > > > It's the only logical explanation. > > > > Russ
