From owner-freebsd-hackers Sat Jul 29 18:23:53 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id SAA08942 for hackers-outgoing; Sat, 29 Jul 1995 18:23:53 -0700 Received: from kaiwan.kaiwan.com (kaiwan.kaiwan.com [198.178.203.2]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id SAA08931 for ; Sat, 29 Jul 1995 18:23:03 -0700 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.12/8.6.12) with UUCP id SAA26522; Sat, 29 Jul 1995 18:22:35 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.8/8.6.6) id SAA00835; Sat, 29 Jul 1995 18:15:46 -0700 From: Frank Mayhar Message-Id: <199507300115.SAA00835@exit.com> Subject: Re: pthreads To: julian@ref.tfs.com (Julian Elischer) Date: Sat, 29 Jul 1995 18:15:46 -0700 (PDT) Cc: terry@cs.weber.edu, bakul@netcom.com, freebsd-hackers@freebsd.org In-Reply-To: <199507300010.RAA07970@ref.tfs.com> from "Julian Elischer" at Jul 29, 95 05:10:07 pm X-Mailer: ELM [version 2.4 PL24 ME5a] Content-Type: text Content-Length: 680 Sender: hackers-owner@freebsd.org Precedence: bulk > Kirk McKusic and co. had a discussion on this topic > when I didi the BSD4.4 course at UCB.. > they were of the opinion that with recent changes to the > efficiency of forking, the answer was to create the new > 'rfork' call, where a forking process can decide what resources it wants > to share with it's child.. > options include: > text space data space, stacks, file descriptor tables etc. This might be a good idea, but 'rfork' might not be such a good name for the call, since it connotes 'remote' rather than 'resource' and certain builders of distributed systems have already co-opted that system call name for a 'remote fork' facility. -- Frank Mayhar frank@exit.com