From: "Steven J. Magnani" <steve@digidescorp.com>
To: Shea Levy <shea@shealevy.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Alternative to vfork(2) with overcommit off
Date: Mon, 30 Jul 2012 12:16:39 -0500 [thread overview]
Message-ID: <1343668599.2153.12.camel@iscandar.digidescorp.com> (raw)
In-Reply-To: <EC19EF84-3DD4-4B5A-9469-2EC11EE089D6@shealevy.com>
On Mon, 2012-07-30 at 12:59 -0400, Shea Levy wrote:
> Hello,
>
> The vfork(2) manpage states "It is rather unfortunate that Linux revived this specter from the past", but on systems with overcommit turned off fork(2) can be needlessly prohibitive when the goal is to execve(2) right away. Is there a third alternative for the fork/execve case? If not, should the manpage really be so dismissive of vfork?
On noMMU (embedded) systems, fork() is not implementable and vfork() is
the only option.
Not everyone can afford a Lexus.
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
prev parent reply other threads:[~2012-07-30 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 16:59 Alternative to vfork(2) with overcommit off Shea Levy
2012-07-30 17:16 ` Steven J. Magnani [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1343668599.2153.12.camel@iscandar.digidescorp.com \
--to=steve@digidescorp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shea@shealevy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox