4 ms·
yeah, that's why vfork has been introduced back in the days. See http://man7.org/linux/man-pages/man2/vfork.2.html http://man7.org/linux/man-pages/man2/vfork.2.
by ithkuil 10y ago
yeah, that's why vfork has been introduced back in the days.
See http://man7.org/linux/man-pages/man2/vfork.2.html http://man7.org/linux/man-pages/man2/vfork.2.html
- the_why_of_y 10y agoThe "historic description" in the man page you cite disagrees: vfork(2) was added before BSD had copy-on-write, so the memory was actually copied and vfork(2) is essentially a crude hack to avoid that. Unfortunately once copy-on-write was implemented, the crude hack was retained for backwards compatibility....