27 Jun
2016
27 Jun
'16
9:17 p.m.
Ronald Natalie <ron(a)ronnatalie.com> wrote:
vfork() is of use on non-paged (and poorly implemented
paging) systems. If you implemented the copy-on-write fork() behavior, you???d not need
the vfork KLUDGE.
This is what the Linux people believe. As a result, they have a vfork()
implementation that collects all pitfalls from fork() and vfork() ;-)
The basic difference is:
- With a copy-on-write fork, you copy an address space description and
need to set up a set of new MMU PTEs.
- With vfork, you borrow the address space descrition and the MMU PTEs
from the parent.
Jörg
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling(a)fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/
http://sourceforge.net/projects/schilytools/files/'