From owner-freebsd-threads@FreeBSD.ORG Mon Apr 21 17:30:40 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 44F5437B407 for ; Mon, 21 Apr 2003 17:30:40 -0700 (PDT) Received: from speicher.org (sirius.speicher.org [209.74.10.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id D648543FE9 for ; Mon, 21 Apr 2003 17:30:38 -0700 (PDT) (envelope-from geoff@speicher.org) Received: from localhost (geoff@localhost) by speicher.org (8.11.6/8.11.6) with ESMTP id h3M0j6Q60496; Mon, 21 Apr 2003 20:45:06 -0400 (EDT) (envelope-from geoff@speicher.org) Date: Mon, 21 Apr 2003 20:45:06 -0400 (EDT) From: "Geoffrey C. Speicher" To: Jeff Roberson In-Reply-To: <20030421190831.S76635-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: Daniel Eischen cc: Julian Elischer 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: Tue, 22 Apr 2003 00:30:40 -0000 On Mon, 21 Apr 2003, Jeff Roberson wrote: > 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. > > Uh, no, it's not that clear. One is probably 30k lines of code smaller > which makes it less likely to have bugs. They also have different > performance characteristics. You could construct tests which demonstrated > better performance for different workloads on each. I will not deny that you are correct on all of the above, but bugs will be fixed, and inefficiencies will be corrected. Then we will have two very similar things in terms of stability and performance under 1:1 threading. One will also have support for 1:N and M:N, and the other will not. I do not mean to take anything away from your work, which is valuable for many reasons, but I really do think that the long-term goal should be more cooperation to make libkse perform as well as libthr in the 1:1 case once everything has shaken out rather than maintain them under separate tents. Geoff