From owner-freebsd-current Sat Oct 31 13:28:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19288 for freebsd-current-outgoing; Sat, 31 Oct 1998 13:28:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19281 for ; Sat, 31 Oct 1998 13:28:10 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA10997; Sun, 1 Nov 1998 08:35:32 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810312135.IAA10997@cimlogic.com.au> Subject: Re: Kernel threading (was Re: Thread Scheduler bug) In-Reply-To: <199810312118.NAA00662@dingo.cdrom.com> from Mike Smith at "Oct 31, 98 01:18:12 pm" To: mike@smith.net.au (Mike Smith) Date: Sun, 1 Nov 1998 08:35:32 +1100 (EST) Cc: jb@cimlogic.com.au, lists@tar.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > It sounds like the two of you should cooperate on it then; Richard has > clearly managed to get his head around at least some of the kernel > issues, while you're on top of the user-space stuff. I think that the code in the FreeBSD kernel is inappropriate for a POSIX thread implementation. The syscall design needs to change. And the management of pid entries for threads needs to change too. Then there are the multi-architecture issues. I doubt that I'll have time in the next 6 months. Unless someone finds some dollars. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message