Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Oct 2006 19:38:14 +1300
From:      Mark Kirkwood <markir@paradise.net.nz>
To:        Julian Elischer <julian@elischer.org>
Cc:        Greg Lewis <glewis@eyesbeyond.com>, Paul Allen <nospam@ugcs.caltech.edu>, Lev Serebryakov <lev@freebsd.org>, Robert Watson <rwatson@freebsd.org>, current@freebsd.org
Subject:   Re: KSE, libpthread & libthr: almost newbie question
Message-ID:  <45459DD6.6070309@paradise.net.nz>
In-Reply-To: <45458C7E.50104@elischer.org>
References:  <917908193.20061027102647@serebryakov.spb.ru> <20061027103924.F79313@fledge.watson.org> <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>

next in thread | previous in thread | raw e-mail | index | archive | help
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?
>

I stumbled on link below while doing a little searching on this topic:

http://java.sun.com/j2se/1.5.0/docs/guide/vm/thread-priorities.html

Obviously Solaris and Java centric, but discussed the M:N to 1:1 change 
between 1.4.1 and 1.4.2 along with the Java threads <-> lightweight 
process representation.

regards

Mark



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45459DD6.6070309>