From owner-freebsd-current@FreeBSD.ORG Mon Oct 30 19:26:46 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7F3C16A4FD; Mon, 30 Oct 2006 19:26:46 +0000 (UTC) (envelope-from prvs=julian=45182861c@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4614543EB3; Mon, 30 Oct 2006 19:22:27 +0000 (GMT) (envelope-from prvs=julian=45182861c@elischer.org) Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229]) by a50.ironport.com with ESMTP; 30 Oct 2006 11:22:11 -0800 Message-ID: <454650E2.3040604@elischer.org> Date: Mon, 30 Oct 2006 11:22:10 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: Greg Lewis References: <45426071.7020403@elischer.org> <602423478.20061028001449@serebryakov.spb.ru> <4542896D.1050001@elischer.org> <20061027231642.GJ30707@riyal.ugcs.caltech.edu> <45429703.8070305@elischer.org> <20061028104741.Q69980@fledge.watson.org> <45442A35.2030803@elischer.org> <20061029090309.T27107@fledge.watson.org> <20061029182108.GA46604@misty.eyesbeyond.com> <45458C7E.50104@elischer.org> <20061030163327.GA22419@misty.eyesbeyond.com> In-Reply-To: <20061030163327.GA22419@misty.eyesbeyond.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Paul Allen , Lev Serebryakov , Robert Watson , current@freebsd.org Subject: Re: KSE, libpthread & libthr: almost newbie question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 19:26:47 -0000 Greg Lewis wrote: > On Sun, Oct 29, 2006 at 09:24:14PM -0800, Julian Elischer wrote: >> Greg Lewis wrote: >> >>> If you really want to know, just send the running process a SIGQUIT and >>> it will dump the currently running threads to stdout. But yes, 1.4 and 1.5 >>> both use "native" threads which correspond 1:1 with OS threads (plus >>> there are threads the JVM creates itself, as you note). The JVM threads >>> include garbage collection and AWT event handlers at least. >>> >> I gather it doesn't use libpthread, but rather just the syscalls? > > No, it does use libpthread (or libthr, or libc_r if you so choose). What > I'm saying is that the JVM maps a single Java thread to a single library of your choice> thread. How that maps to a kernel thread is > then defined by the threading library. > > The point is that the JVM doesn't do any internal M:N business itself, > which was the original point under discussion IIRC. > gotcha