From owner-freebsd-threads@FreeBSD.ORG Fri May 23 23:06:42 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 48BA837B401 for ; Fri, 23 May 2003 23:06:42 -0700 (PDT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EA3C43F75 for ; Fri, 23 May 2003 23:06:41 -0700 (PDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h4O66XX56431; Sat, 24 May 2003 02:06:33 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sat, 24 May 2003 02:06:33 -0400 (EDT) From: Jeff Roberson To: Petri Helenius In-Reply-To: <08c401c32143$7843a390$c02a40c1@PETEX31> Message-ID: <20030524020525.D69975-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Daniel Eischen cc: freebsd-threads@freebsd.org Subject: Re: basic thread question 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: Sat, 24 May 2003 06:06:42 -0000 On Fri, 23 May 2003, Petri Helenius wrote: > > > > Either link to libkse or libthr (-lkse or -lthr). Don't use > > libc_r (-pthread or -lc_r). Libkse will set the concurrency > > to the number of CPUs in your system. You can also use > > scope system threads with libkse. > > > > libthr will create each thread in its own KSE, and is more > > like Linuxthreads (1:1) model. libkse is M:N. > > > As far as my experience shows linuxthreads has issues with mutexes on an SMP > machine (at least when running on FreeBSD). libthr does not have issues with mutexes. I'm not sure what linux threads issues are. You should try libthr as well. It has some advantages over kse as well as some disadvantages. > > I actually tried -lkse on a machine with kernel about two weeks old, > so far I have not been able to reach the machine since ... > > Will try again on more local box, because it does not seem to crash to console > debugger but just plain out "die". > > Pete > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >