From owner-freebsd-arch Tue Nov 2 6:32:36 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 5324A15139 for ; Tue, 2 Nov 1999 06:32:27 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id PAA20849 for ; Tue, 2 Nov 1999 15:32:22 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA80166 for freebsd-arch@freebsd.org; Tue, 2 Nov 1999 15:32:21 +0100 (MET) Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id D9E7B153E3 for ; Tue, 2 Nov 1999 06:28:05 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id IAA28100; Tue, 2 Nov 1999 08:27:59 -0600 (CST) (envelope-from dick) Date: Tue, 2 Nov 1999 08:27:59 -0600 From: "Richard Seaman, Jr." To: Julian Elischer Cc: freebsd-arch@freebsd.org, rcarter@pinyon.org Subject: Re: Threads models and FreeBSD. (Next Step) Message-ID: <19991102082758.D5715@tar.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 02, 1999 at 12:59:28AM -0800, Julian Elischer wrote: [.....] > We have 4 starters at this point. Note, they MAY NOT BE mutually > exclusive! > > 1/ The scheme we've been working towards for a while due to lack of > suggested alternatives.. rfork based processes sharing resources. > This is very similar to the Linuxthreads implementation. one kernel > schedulable entity (light process) per thread. > 1A/ actually use the linuxthread code.. FYI Russell Carter has updated the linuxthread port, and has indicated to me an interest in taking over this project, since I haven't had time to work on it lately. Be aware that the linuxthread port uses an older version of linuxthreads. While newer versions may not be that hard to bring over, it appears that the new linuxthreads will start to rely on features of the linux kernel that will have to be implemented in the FreeBSD kernel (eg. threads sharing the parent pid). This may well be necessary anyway for the linux emulator, but in general using linuxthreads will put you in the position of having to implement linux kernel features that the linuxthreads library needs. I have some thoughts on using the existing uthread to move to m/n user/kernel threads that I will try to put down later. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message