From: Eric Cooper <ecc@cmu.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] re: We should all be forking
Date: Tue, 5 Jun 2007 18:53:33 -0400 [thread overview]
Message-ID: <20070605225333.GB30687@stratocaster.home> (raw)
In-Reply-To: <20070605223047.GB30586@yumegakanau.org>
On Tue, Jun 05, 2007 at 03:30:47PM -0700, Christopher Cramer wrote:
> If the fork had to copy the entire process image before just
> throwing it away upon exec, I think Unix, which is based around a
> philosophy of piping between multiple processes, would have
> abandoned fork a long time ago. Then again, there is vfork, so I
> guess they almost did abandon it at one point.
vfork was introduced in BSD Unix when support for page-based virtual
memory was added for the DEC VAX. There was an earlier Bell Labs
port of Unix to the VAX that just mimicked the PDP-11's segment
registers. In that scheme, I believe text segments were shared, so
that only the data segment had to be copied on fork, but copy-on-write
is the way to go on any architecture with page tables.
--
Eric Cooper e c c @ c m u . e d u
next prev parent reply other threads:[~2007-06-05 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 22:30 Christopher Cramer
2007-06-05 22:53 ` Eric Cooper [this message]
2007-06-06 9:28 ` [Caml-list] " Oliver Bandel
2007-06-06 17:51 ` Shawn W.
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=20070605225333.GB30687@stratocaster.home \
--to=ecc@cmu.edu \
--cc=caml-list@inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).