From owner-freebsd-hackers  Fri Jan 31 12:33:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA10504
          for hackers-outgoing; Fri, 31 Jan 1997 12:33:03 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10499
          for <freebsd-hackers@freebsd.org>; Fri, 31 Jan 1997 12:32:59 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id NAA15001; Fri, 31 Jan 1997 13:32:14 -0800 (PST)
Message-ID: <XFMail.970131133213.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <9701301753.AA23376@wavehh.hanse.de>
Date: Thu, 30 Jan 1997 23:38:31 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: cracauer@wavehh.hanse.de
Subject: Re: Using rfork() / threads
Cc: freebsd-hackers@freebsd.org, rminnich@Sarnoff.COM,
        (Martin Cracauer) <cracauer@wavehh.hanse.de>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi Martin Cracauer;  On 30-Jan-97 you wrote: 
> rminnich@Sarnoff.COM (Ron G. Minnich) wrote:
> 
> [rfork]
> 
> >VM space handling is a little different. If you request VM space sharing,
> >you don't exactly get Vm address space sharing:  what you get is instead
> >shared data areas where in normal fork they are copied. More details on 
> >request. The effect is what you want, though: shared data areas. 
> 
> Could you explain a bit more. What exactly is the difference between
> VM space sharing and shared data areas from the process' and the
> kernel perspective?

Yes please, in perspective of the Linux clone(2) and the new libc 2.0
threads, etc.

Thanx, Simon