From owner-freebsd-threads@FreeBSD.ORG Thu Apr 3 14:39:45 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E63B637B401 for ; Thu, 3 Apr 2003 14:39:45 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4511943FA3 for ; Thu, 3 Apr 2003 14:39:45 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0138.cvx21-bradley.dialup.earthlink.net ([209.179.192.138] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 191DMq-0004hc-00; Thu, 03 Apr 2003 14:39:33 -0800 Message-ID: <3E8CB7D3.A4B3CBF7@mindspring.com> Date: Thu, 03 Apr 2003 14:38:11 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Eischen References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4618e752b7c97411a3326757fdd7254b5548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: "Geoffrey C. Speicher" cc: freebsd-threads@freebsd.org Subject: Re: 1:N threading X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 22:39:46 -0000 Daniel Eischen wrote: > Libc_r will go bye-bye. The KSE library will give you 1:N > as long as you don't use pthread_setconcurrency() and don't > create any PTHREAD_SCOPE_PROCESS threads. I think that maybe you need to get over the "fear factor" here. Specifically, it's probably time to commit a "libkse", the same way that Jeff committed a "libthr", so that it doesn't directly replace "libc_r", and leave people hanging over a cliff if it has a bug. Better to take an approach that doesn't piss people off, but gets the code to a wider audience. Is this a possibility? The only thing that seems screwed up is the signals processing. Jeff's code panic's the system with a lock order reversal on exit processing, under some circumstances, but it's tolerated because it didn't outright replace "libc_r", and offer an alternative to "conservative" -CURRENT users. -- Terry