Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!apple!sun-barr!ccut!titcca!cc.titech.ac.jp!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.arch
Subject: Re: vfork() and swap space allocation
Message-ID: <5897@titcce.cc.titech.ac.jp>
Date: 19 Jul 90 08:17:30 GMT
References: <5813@titcce.cc.titech.ac.jp> <2699E08D.117A@tct.uucp> <5844@titcce.cc.titech.ac.jp> <269DBEFB.583C@tct.uucp> <+FP4PP@xds13.ferranti.com>
Sender: news@cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 13

In article <+FP4PP@xds13.ferranti.com>
	peter@ficc.ferranti.com (Peter da Silva) writes:

>> Note the "except" clause.  Mr. Masataka himself here points out that
>> vfork() is an incomplete solution, since a kernel with vfork() must be
>> prepared to deal gracefully with swap space exhaustion due to stack
>> modification.

>Is it absolutely necessary to clone the stack segment in a vfork() call?

It is absolutely unnecessary, thus, not done. Stack segment is shared.

							Masataka Ohta