From owner-freebsd-threads@FreeBSD.ORG Mon Apr 21 16:12:19 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 81FF737B401 for ; Mon, 21 Apr 2003 16:12:19 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B1D243FE3 for ; Mon, 21 Apr 2003 16:12:18 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h3LNCGUE031252; Tue, 22 Apr 2003 02:12:16 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost)h3LNCGjp031249; Tue, 22 Apr 2003 02:12:16 +0300 (EEST) Date: Tue, 22 Apr 2003 02:12:16 +0300 (EEST) From: Narvi To: "Geoffrey C. Speicher" In-Reply-To: Message-ID: <20030422020939.S29990-100000@haldjas.folklore.ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: libkse -> libpthreads 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: Mon, 21 Apr 2003 23:12:19 -0000 On Mon, 21 Apr 2003, Geoffrey C. Speicher wrote: > On Tue, 22 Apr 2003, Narvi wrote: > > > At least for the moment it is not clear that one of teh libraries is a > > winner and will eliminate the other, so it would be evil to force people > > What's not clear about it? libkse is a superset of the functionality > of libthr. Seems pretty straightforward to me that the long-term > winner is libkse. > This assumes that libkse M:N model will provide supperior performance and scalability, and this is not clear. Or does merely the fact that itis M:N somehow make it more winning contender? > > to explicitly link against one or the other causing future compatibility > > problems. Both provide the same pthreads API so there is no reasonable > > case for demanding that one of them can't have its SONAME be > > libpthpread.so.1 > > Same API, but different capabilities. The one called pthread should be > the complete one. No compatability problems in that direction. > > Geoff >