This is the mail archive of the
mailing list for the GCC project.
Re: Is there any reason to use vfork() ?
- From: Florian Weimer <fweimer at redhat dot com>
- To: niXman <i dot nixman at autistici dot org>, gcc at gcc dot gnu dot org
- Date: Wed, 14 May 2014 09:33:42 +0200
- Subject: Re: Is there any reason to use vfork() ?
- Authentication-results: sourceware.org; auth=none
- References: <db279b78b31710a4d4a38e37817520e9 at autistici dot org>
On 05/13/2014 12:12 PM, niXman wrote:
I'm curious whether there is reason to use 'vfork()' rather than 'fork()'?
Without memory overcommitment, fork needs physical backing storage (RAM
or swap) for all copy-on-write pages in the new process. vfork doesn't.
Florian Weimer / Red Hat Product Security Team