From owner-freebsd-current Fri Aug 7 00:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12328 for freebsd-current-outgoing; Fri, 7 Aug 1998 00:14:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com (port25.prairietech.net [208.141.230.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12243 for ; Fri, 7 Aug 1998 00:14:17 -0700 (PDT) (envelope-from alk@pobox.com) Received: (from alk@localhost) by pobox.com (8.8.8/8.7.3) id CAA18096; Fri, 7 Aug 1998 02:15:48 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 7 Aug 1998 02:15:47 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13770.43121.617719.400946@compound.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : From: John Birrell : Amancio Hasty wrote: : > Curious, whats missing from the kernel for us to have kernel threads? : The last problem I was having was with the user_ldt being restored : on context switches. ...patches I sent... : I'd suggest that it is too close to the release of 3.0 to try to get : that stuff in, except possibly for the syscalls. Ouch! Like some (many?) others, in my world the whole value of 3.0 is wrapt in SMP and kernel threads. Nothing else counts, comparatively speaking. : It is better to get : 3.0 to a stable state to limit the flak from people who don't (won't) : understand why 2.2.8 will come out after 3.0. How about delaying the release long enough to include the significant added value, thereby reducing the gap between 2.2.8 and 3.0, thereby reducing the flak from the quarter you posit, as well as the flak from my own kindred spirits? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message