Hi all,
Here's a problem I've wrestled with off and on... I have an aggregation
keyed off ustack(), and if the process exits before dtrace stops, I get
the usual hex garbage for the resulting stack frame printouts.
I know the usual way to deal with this is by stopping the process, but
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
It's used to put threads to sleep that are blocking on user locks
(at least that's my recollection).
Run prstat -Lmp PID_OF_APP) - what does the LCK column look like?
Try running plockstat -A -p PID_OF_APP.
Thanks,
/jim
Dtrace Email wrote:
Hi, when doing dtrace on an appliction,
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 james.ma...@sun.com wrote:
It's used to put threads to sleep that are blocking on user locks
(at least that's my
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 PID_OF_APP) - what does the LCK column look like?
Try running
