First, thanks to Andrew for referencing my paper. Although it was
written for the great Solaris 9 thread model U-turn, a lot of what it
says still applies today (except that the thread library has now been
folded into libc).
If you're using the DTrace syscall provider you will only see lwp_par
Yes. Lots of info in
http://www.sun.com/software/whitepapers/solaris9/multithread.pdf
Jim Mauro wrote:
It's used to put threads to sleep that are blocking on user locks
(at least that's my recollection).
Run "prstat -Lmp .
Thanks,
/jim
Dtrace Email wrote:
Hi, when doing dtrace on an appli
Yep. The system call is lwp_park(). Given that it's a blocking
system call, the time a thread spends here is effectively unbounded.
Chad
On Wed, Feb 3, 2010 at 3:47 PM, Jim Mauro wrote:
> It's used to put threads to sleep that are blocking on user locks
> (at least that's my recollection).
>
>
It's used to put threads to sleep that are blocking on user locks
(at least that's my recollection).
Run "prstat -Lmp .
Thanks,
/jim
Dtrace Email wrote:
Hi, when doing dtrace on an appliction, __lwp_park() seems to be taking a lot
of time. What does it really do? is it waiting for thread
Hi, when doing dtrace on an appliction, __lwp_park() seems to be taking a lot
of time. What does it really do? is it waiting for threads?
Thanks,
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris
