From owner-freebsd-current Sat Oct 31 14:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26289 for freebsd-current-outgoing; Sat, 31 Oct 1998 14:38:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26284 for ; Sat, 31 Oct 1998 14:38:04 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id QAA24079; Sat, 31 Oct 1998 16:37:48 -0600 (CST) Message-Id: <199810312237.QAA24079@ns.tar.com> From: "Richard Seaman, Jr." To: "Jordan K. Hubbard" Cc: "John Birrell" , "current@freebsd.org" Date: Sat, 31 Oct 98 16:37:47 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Kernel threading (was Re: Thread Scheduler bug) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 31 Oct 1998 14:08:43 -0800, Jordan K. Hubbard wrote: >I agree. While not perhaps adopting the perfect approach, at least >Richard brings some very welcome *movement* to an issue which has been >stalled for a regrettably long period of time. Let's try to run >(cooperatively) with this and hopefully arrive at some working, >architecturally clean kernel threads for FreeBSD! Just to be clear. I'm happy to co-operate and share code with anyone. In fact, I'd be happy for someone else to just handle it all. In the absence of someone else will to handle it all, I'm happy to contribute what I can. The *only* reason I'd be hesitant to share any code at this moment is that its still pretty messy, and I'd be embarrassed, and since its barely tested, people would rightfully shoot all kinds of holes in it. When its in a better state I'd be happy to post it somewhere where anyone can whack at it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message