From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 09:52:37 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DB4337B404 for ; Thu, 22 May 2003 09:52:37 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id D16EE43F85 for ; Thu, 22 May 2003 09:52:36 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h4MGqU8f086751; Thu, 22 May 2003 11:52:30 -0500 (CDT) (envelope-from dan) Date: Thu, 22 May 2003 11:52:30 -0500 From: Dan Nelson To: Terry Lambert Message-ID: <20030522165229.GA1694@dan.emsphone.com> References: <20030522042922.GC13024@dan.emsphone.com> <3ECCF855.6A0E8830@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3ECCF855.6A0E8830@mindspring.com> X-OS: FreeBSD 5.1-BETA X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org cc: Daniel Eischen cc: Julian Elischer Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2003 16:52:38 -0000 In the last episode (May 22), Terry Lambert said: > Make sure you use SCHED_4BSD, rather than SCHED_ULE, if you are using > one of the kernel threads libraries, for now. > > You really should read the -current archives before attempting any of > this, if you don't follow -current closely enough to have caught > Jeff's message on this, or which kernel threading libraries are > available. I do read -current, and I'm definitely not going anywhere near SCHED_ULE. I just tested both libraries with today's kernel and libraries, and was able to get a hard lockup with both libthr and libkse. Mysql seems to run okay. Starting a threaded pike process seems to be the killer. Unfortunately, pike's a pretty large app so it's not easy to get a stripped-down testcase. -- Dan Nelson dnelson@allantgroup.com