From owner-freebsd-threads@FreeBSD.ORG Fri May 23 11:18:12 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 613C537B401 for ; Fri, 23 May 2003 11:18:11 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCF1A43F93 for ; Fri, 23 May 2003 11:18:10 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by attbi.com (sccrmhc02) with ESMTP id <20030523181809002002jstqe>; Fri, 23 May 2003 18:18:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA92084; Fri, 23 May 2003 11:18:08 -0700 (PDT) Date: Fri, 23 May 2003 11:18:08 -0700 (PDT) From: Julian Elischer To: Petri Helenius In-Reply-To: <08c401c32143$7843a390$c02a40c1@PETEX31> Message-ID: 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: Fri, 23 May 2003 18:18:13 -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). > > 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". Also make sure you have newest code.. We do have a problem where the system seems to crash but it's not at all reproducible and I'm pulling my hair out trying to find it.. > > 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" >